-
Notifications
You must be signed in to change notification settings - Fork 120
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
deps: Bump eslint suite to v9 #1565
Conversation
Migrated the eslint config using `npx @eslint/migrate-config .eslintrc.json`, and did not work flawlessly, obviously I had to include config to examples into the root config file. Instead, we are able to delete `.eslintrc` that existed for each example directory though `require-atomic-updates` (has been set to `off`) does not exist in the default configs, so removed the line `@typescript-eslint/no-unnecessary-type-assertion` requires a type assertion, removed it for now
parentBoneName ?? (parentBoneName = 'hipsParent'); | ||
if (parentBoneName == null) { | ||
parentBoneName = 'hipsParent'; | ||
} |
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.
Do you mean
parentBoneName ?? (parentBoneName = 'hipsParent'); | |
if (parentBoneName == null) { | |
parentBoneName = 'hipsParent'; | |
} | |
parentBoneName ??= 'hipsParent' |
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.
Tested locally and found two issues
.eslintrc.json
is a leftover?- lint runs fine for packages but shows warning when opening
eslint.config.mjs
andjest.config.mjs
seem to be errors of |
These `@typescript-eslint/naming-convention` errors can be easily fixed by inserting brackets Addresses: #1565 (review)
This PR bumps eslint suite to v9.
This also migrates the existing eslint configs to the new flat config.
See the commit logs for details.