Thomas Lindner
Thomas Lindner
Thanks, @dietergeerts. I'm moving (slowly) through v4. I'm hoping this will be a part of it. Do you have any thoughts on your preferred interface for writing custom rules? I'm...
Nice work, @mightyiam. This is looking really good. Let me know if you have questions about my comments. I'm happy to discuss more!
Thank you, @piranna! I take a look at this tomorrow and get back to you.
@piranna do you think [`valid-values-name-scope`](https://npmpackagejsonlint.org/docs/en/rules/valid-values/valid-values-name-scope) will meet your needs? `error` covers `always`. `off` covers `don't care`. `never` is a gap. btw - I've got time this weekend to get caught...
@piranna - yes, re: `@`. Do you have any concerns with that approach? I'm going to focus on adding plugin support next. Do you have an immediate use case for...
Hey @bentruyman - thank you for using the project! This is a great suggestion! I like your recommendation to start with those two rules.
Hey @piranna - you are correct. v4 added the fix flag to the cli interface, but nothing has been implemented behind it. v3 and v4 went through some pretty major...
Hey Bob! Sorry that the docs are confusing! * `require-license` enforces that the license field is present and of the right type (i.e. String). It doesn't enforce a specific license....
Hey @AuHau! That sounds like a great rule idea. You might be able to build off the following rules. What are you thinking about the name for the rules? What...
Hey @Raynos your proposal looks really good! Would you be interested in contributing a PR with the changes?