Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Invalid Apex syntax leads to silent failure #152

Open
jfeingold35 opened this issue Dec 11, 2024 · 4 comments
Open

[BUG] Invalid Apex syntax leads to silent failure #152

jfeingold35 opened this issue Dec 11, 2024 · 4 comments
Labels
BUG P3 Rarely Malfunction

Comments

@jfeingold35
Copy link
Collaborator

Have you verified this is Salesforce Code Analyzer Extension specific?

Yes

Bug Description

When using the VSCode extension to scan invalid code, the result will be "no violations found" instead of throwing an error about the invalid syntax.

Steps To Reproduce

  1. Write an extremely simple Apex class with scope public
  2. Change public to banana
  3. Save the file
  4. Run the VSCode Scanner Extension against this file
  5. Observe that the result is "no violations found".

Expected Behavior

There should probably be an error visible to the user.

Operating System

Any

Visual Studio Code Version

Latest

Salesforce Code Analyzer Extension Version

1.4.0

Salesforce CLI Version

@salesforce/cli/2.58.7 darwin-arm64 node-v20.14.0

Code Analyzer CLI Plugin (@salesforce/sfdx-scanner) Version

@salesforce/[email protected]

Additional Context (Screenshots, Files, etc)

No response

Workaround

No response

Urgency

Low

@jfeingold35
Copy link
Collaborator Author

This issue was first logged on the SFDX Scanner repo as forcedotcom/sfdx-scanner#1694.

@jfeingold35 jfeingold35 added the BUG P3 Rarely Malfunction label Dec 11, 2024
Copy link

git2gus bot commented Dec 11, 2024

This issue has been linked to a new work item: W-17409257

@EricsIssue
Copy link

@jfeingold35 I have both salesforce extension packs installed for vs code & neither one shows any red line nor indicate errors.
.
image

image

@jfeingold35
Copy link
Collaborator Author

jfeingold35 commented Dec 11, 2024

That sounds like an issue with one of the other extensions in the extension pack, and you may wish to raise that with the team that owns the Apex extension, which you can do here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG P3 Rarely Malfunction
Projects
None yet
Development

No branches or pull requests

2 participants