-
-
Notifications
You must be signed in to change notification settings - Fork 112
Add support for custom rules #250
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
base: master
Are you sure you want to change the base?
Conversation
This adds a textarea in the settings page that can be used to enter custom rules in the same format as data.json. These rules are applied on top of the ones from data.json.
start.getKeys() was using a for...in loop to iterate over fields in the given object, meaning that methods names (e.g. getOrDefault()) get included in the iteration as well. This causes erroneous entries to be added the global list of providers. Fix this by using Object.keys() to extract field names and iterate over that instead.
Kudos, SonarCloud Quality Gate passed!
|
That's exactly what I was looking for in the extension options, thinking this was a base feature. |
Good idea. It will also help to submit improved rules to the core set, as advanced users may test the rules easier. |
Please merge it :s |
@KevinRoebert this PR exists for more than two years now, could you please merge it or decline, so that we all know how things are with this feature? |
Add this feature please |
This adds a textarea in the settings page that can be used to enter custom rules in the same format as data.json. These rules are applied on top of the ones from data.json.