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

[Feature Request] To be able to specify --category for scanning code violations in Extension Settings #10

Open
vc4u opened this issue Sep 10, 2023 · 2 comments
Labels
USER STORY New feature or request

Comments

@vc4u
Copy link

vc4u commented Sep 10, 2023

Is your feature request related to a problem? Please describe.
By default the scan finds and flags almost every violations and warning which could be overwhelming for a large class.

Describe the solution you'd like
It would help ISVs, to be able to scan for just "Security" category so as to be ready to generate report for Security Review submission.

"Workaround":
Executing via CLI allows category argument to scan only for Security concerns.

"Urgency":
Nice to have

@jfeingold35
Copy link
Collaborator

@vc4u , in the long-term, we may add some mechanism to more finely control which rules run in the extension. But for now, per the documentation, you could create a custom PMD config file that includes only the Security rules, and reference that in the extension's settings. Then only those rules will run.

@jfeingold35 jfeingold35 added the USER STORY New feature or request label Sep 18, 2023
@git2gus
Copy link

git2gus bot commented Sep 18, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
USER STORY New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants