devops: switch to @tony.ganchev/eslint-plugin-header#2031
devops: switch to @tony.ganchev/eslint-plugin-header#2031tonyganchev wants to merge 1 commit intoIBM:mainfrom
Conversation
Reasons: - The fork is supported and updated. - ESLint 9-native with full schema support and needing no hacks. - Windows support - Multiple other bugfixes. - UX improvements - better error messages and more autofix capabilities. - Extensive documentation. - Better configuration format (although the old one is still supported). Signed-off-by: Tony Ganchev <tony.ganchev@gmail.com>
|
Thank you for proposing this change. |
| import customTsRules from './.eslint-rules-ts.mjs'; | ||
|
|
||
| // Disable schema checking for eslint-plugin-header | ||
| header.rules.header.meta.schema = false; |
There was a problem hiding this comment.
@ricellis I just realized I did not clear out this hack from the PR. This is the immediate benefit of not using the original project.
Thanks, makes sense. Please take a look at the comment above - the ugly hack that was needed so that eslint-plugin-header is no longer needed but I forgot to remove it in this PR. |
PR summary
Reasons:
Fixes: (not sure if non-maintainers should spam with devops issues).
PR Checklist
Please make sure that your PR fulfills the following requirements:
Angular Commit Message Guidelines.
PR Type
What is the current behavior?
N/A
What is the new behavior?
N/A
Does this PR introduce a breaking change?
Other information