Skip to content

Latest commit

 

History

History
128 lines (127 loc) · 4.2 KB

File metadata and controls

128 lines (127 loc) · 4.2 KB
NameAboutLabelsAssignees
Report a Bug with a code-analyzer commandReport an issue with a code-analyzer command.

Oftentimes, you can resolve code-analyzer issues on your own. Follow these steps:

  1. Read the error message.
  2. Read Salesforce Code Analyzer documentation.
  3. Double-check the command that you ran. Ensure that items like file names, method names, and category names are correctly spelled and cased.
  4. Verify that your code is syntactically valid.
  5. Verify that the error is reproducible on another machine.
  6. Check open and closed issues to see if your issue is already logged.

I confirm that I have gone through these steps and still have an issue to report.
(You must select "Yes" to create an issue.)

Provide a clear and concise description of what the bug is and include the exact command that you ran.

Attach any output or logs here

List out the steps that you used to reproduce the bug behavior. Be as specific and clear as possible.

Provide a clear and concise description of what you expected to happen.

What is your machine's operating system?

What do you get from the command "sf --version"?

What do you get from the command "sf plugins"?

What do you get from the command "node --version"?

What do you get from the command "java -version"?

What do you get from the command "python --version"?

Add any other context about the problem.

What ways have you found to sidestep the problem? If you haven't found a workaround, what have you tried so far?

What is the severity of the problem?