-
-
Notifications
You must be signed in to change notification settings - Fork 417
feat: add new rule no-array-fill-with-reference-type without fix solution #2661
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
base: main
Are you sure you want to change the base?
Conversation
… imported from ...create-rule.js
…nt-docs using Node.js v22.16.0
…eadme.md to main generated by npm run fix:eslint-docs using Node.js v22.16.0
…nt-docs using Node.js v22.16.0
… imported from ...create-rule.js
…nt-docs using Node.js v22.16.0
…eadme.md to main generated by npm run fix:eslint-docs using Node.js v22.16.0
…nt-docs using Node.js v22.16.0
…e to no mutation to `errors`
OK |
|
@fisker Could you check the CI failures? They don’t appear to be related to this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm having difficulty understanding the logic, will take another look.
|
Please also take a look at https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/new-rule.md |
I ran |
|
@fisker Could you check the lint warnings for me. I have merge main but the warnings still exists: |
…lar case in readme
…ake the function intent more clearer
…apper2) apart so the code paths are easier to follow
#2657