-
Notifications
You must be signed in to change notification settings - Fork 33
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] Custom Rule Integration #208
Comments
Hey @StephenEsser, thanks for using this project! We currently don't have that feature, but it is one of two major features on the roadmap (auto-fixing). I believe the core rules will allow you to achieve the first one. "Disallow specific packages from being listed in dependencies, devDependencies, or peerDependencies."
The other rules look like nice core rules too. What are your thoughts on spinning them off as rule requests?
Regarding custom rule support, would you be okay consolidating this issue with #108? |
Hey @tclindner, I think adding to the list of core rules is a good idea. Feel free to consolidate the custom rule support issues together. I should have taken a closer look at the issue list. The projects I work on would greatly benefit from custom rule integration. I'll check in from time to time to see how things are going with the project. Keep up the good work! |
Summary
I stumbled onto this project after having a similar idea and doing a quick search on the NPM registry. If this functionality already exists please let me know. I didn't see any information on the documentation site regarding custom rules.
There are use cases where certain projects may want to implement custom rule integration. A plugin system similar to adding rules to eslint or stylelint.
Examples of custom rules:
"1.0.0"
vs"^1.0.0"
The text was updated successfully, but these errors were encountered: