How to use the Debugging feature.
The Debugging feature is both powerful and easy to use. It can help you to identify, debug and solve coding issues quickly and easily, increasing your overall efficiency.
In order for the Debugging feature to work properly, the AI needs to receive enough code so that it can understand the context of the code and fix it accordingly. Descriptive names for functions, classes and variables should be used. This type of naming will help the AI understand the context and provide a valid solution.
Log in first with Google Authentication on Kodezi.
After successfully logging in, select the Debugging button for the short method, or use the context menu when right-clicking the code editor.
Kodezi Quick Explorer
Visual Studio Code Context Menu
Kodezi does not support extremely large sections of code, so you may have to select a block of code for debugging if guided to do so.
After clicking the debugging button, the debugging process will start.
You will see results similar to these in your IDE once the debugging process is finished.
You can correct errors by word, line, and one-click to fix all issues.
- 1.Fix Line will fix the issues only on line 57.
- 2.purple button "NEW_LINE" will replace the word "const RevAs=CallReverse()" into a new line.
- 3.Fix All Issues will fix errors at one click and the solution will replace your original file.
The AI's main purpose is to make sure your code is able to be compiled. So if you use the debugging feature and the code is incomplete, the AI will try to complete the code so it can be compiled. Since comments aren't required to make code compile, if there are comments in the code, then, the comments may be removed. Try to input code that is standalone and can be compiled. The following are some examples of good and bad code for debugging;
Good Code Input;
Complete in context, has functions which are being used in other functions present so AI doesn't try to generate it to make the code compilable.
Bad Code Input;
Incomplete in context, functions which being used are not declared in the scope so AI will try to fix this, disrupting the codes flow when the debugged code is integrated back into the original pipeline.