How to pass additional config for a rule
See original GitHub issueHey, the project is awesome!
I would like to use it with import/no-unused-modules
rule from eslint-plugin-import
plugin but not sure how to pass additional config for that rule.
Is there an option do use something like this --rule="{ import/no-unused-modules: [2, { unusedExports: true }] }"
?
Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Managing Your AWS Config Rules
Add, View, Update and Delete Rules (Console) · Type in the search field to filter the list of managed rules by rule name,...
Read more >Simplify Custom Rule Creation Using the AWS Config Rule ...
In this video, you'll see how to simplify custom rule creation using the AWS Config Rule Development Kit (RDK). With this tool, you...
Read more >Remediate Non-Compliance Using AWS Config Rules and a ...
Learn more about AWS at – https://amzn.to/2McIkPL AWS Config ... Remediate Non-Compliance Using AWS Config Rules and a Custom SSM Document.
Read more >Managing Your Amazon Config Rules - 亚马逊云科技
You can use the Amazon Config console, Amazon CLI, and Amazon Config API to view, add, and delete your rules. Add, View, Update...
Read more >put-organization-config-rule - Amazon AWS
If you are adding a new Custom Lambda rule, you first need to create an Lambda function in the management account or a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Makes sense. It should work for me. Thanks for the quick response!
I understood #47 as a request to essentially pre-select a rule from the list and skip the manual selection step.
I’d prefer avoiding another option or changing the way the current option works unless there’s a strong need for it. I think your workaround of creating a special eslint config file is a good one. Instead of duplicating the values from your main config, you should be able to use
extends: 'path/to/main/.eslintrc'
, @carbonid1.