-
Notifications
You must be signed in to change notification settings - Fork 36
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
add --options
to find unused options
#284
Comments
Uh, that's a nice idea 👍 The rules' eslint.linter.getRules().get('indent').meta.schema |
Hi, I'm now analyzing the code for this feature, but I just stuck because I have no idea what is the proper way to display such unused options as an output. For example, you have only specified the first argument ( In this case, what would be the best to show on the output? I guess only first level of the options would be sufficient for everyone: NOTE: The user may need to provide a value to rest of the options to clear the output.
|
Just the names of the options and the rule, and the link to the rule docs, would be sufficient for me. |
Is there an example of what “names of the options and the rule” would look like? For example: https://eslint.org/docs/rules/indent In a rule like “indent”, it may not only accept an object as a options, but also accept primitive values like And there may be nested options where some object can contain another object, what would be the output in this case? |
I’d be interested in the kinds of options unset, but not their potential values unless it’s an enum or a boolean. In the case of indent, the object option keys is what I’m most interested in. |
I'd like to run a command that ensures that for all rules I have defined, I've defined every possible compatible schema option.
For example, for the "indent" rule, http://eslint.org/docs/rules/indent points out that it can have an object option with 12 different options. I'd like a report, for that rule, of any of the 12 I've omitted in my config.
The text was updated successfully, but these errors were encountered: