-
Notifications
You must be signed in to change notification settings - Fork 25
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: Bring in eslint-plugin-node-dependencies's valid-semver rule #49
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Are you thinking this would just be incorporated into the valid-package-definition rule / PJV to tighten the testing of the version version check that it does, or as its own rule? It feels like it could be its own rule. So the valid-package-definition is more about the shape of the package.json being valid, whereas this would be a more granular check of the version ranges? What do you think? |
That's what I'm thinking, yeah. I think |
I see. So this work would start in PJV making it more modular. That's kind of adjacent to this comment I made in the TS PR, suggesting that the large single named export could be deprecated in favor of exporting the individual functions and constants directly: https://github.com/JoshuaKGoldberg/package-json-validator/pull/110/files#diff-1df698d75ae20791f18d3bf63174980da33961f49732636648f671b1921929bfR509-R510 So you're seeing the logic for this still living in PJV, but that it's just broken up more so that this plugin could use different validations for different rules? |
Oh TIL I'm not watching all events on that repo. I'd missed that TS PR! Thanks 😄. And yes, that's what I'm envisioning. I think there will always be a use case for |
Splitting out from #43 (comment) & #42:
eslint-plugin-node-dependencies
has avalid-semver
rule. Let's merge it into this package!https://ota-meshi.github.io/eslint-plugin-node-dependencies/rules/valid-semver.html
Blocked on #40, but once that PR is merged this will be good to go.✅The text was updated successfully, but these errors were encountered: