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

Configuring custom targets for analysis is not possible #657

Open
rromannissen opened this issue Feb 14, 2025 · 1 comment
Open

Configuring custom targets for analysis is not possible #657

rromannissen opened this issue Feb 14, 2025 · 1 comment
Milestone

Comments

@rromannissen
Copy link

rromannissen commented Feb 14, 2025

The current design doesn't allow to configure custom targets for an analysis, only options from the prefixed list of targets that come out of the box with the analyzer are available.

Proposed behavior to implement support for custom targets:

By default, the rules that come out of the box with the plugin are enabled, so we would be offering all the corresponding sources and targets from those rules. That list shouldn't be static though, but calculated from the rules directory that is bundled in the plugin

If the user adds custom rules, then there are two possibilities:

  • The user disables the rules that come out of the box, then only the sources and targets from the custom rules should be displayed

  • The user enables the rules that come out of the box, then the sources and targets to be displayed are the joint list from the rules that come out of the box and the custom rules

Changing custom rules should reset sources and targets selected in previous executions, maybe after a warning message.

@shawn-hurley
Copy link
Contributor

Proposal to change this to tracking issue to "Configuring and using custom rulesets should be fully integrated" or something like that. I would like to add a class of concerns here and track them as meta issues. Alternatively, we can create another issue and add this as one of the children

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

No branches or pull requests

3 participants