-
Notifications
You must be signed in to change notification settings - Fork 994
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
fix(deps): update typescript-eslint monorepo to v8 (major) #11235
Conversation
{ | ||
files: ['*.ts', '*.tsx'], | ||
rules: { | ||
'@typescript-eslint/no-explicit-any': 'off', | ||
'@typescript-eslint/consistent-type-imports': 'error', | ||
}, | ||
}, |
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 moved these from the generic "rules" above because otherwise there was errors related to passing config through the babel parser to the ts-eslint parser
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 we care about .mts? No biggie either way
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.
Yeah good spot! I noticed that in some of the tinkering I did earlier today outside this PR. I'll make sure to add this in some follow up work.
@@ -154,7 +154,8 @@ module.exports = { | |||
// 'recommended' rules we alter | |||
'@typescript-eslint/no-explicit-any': 'warn', | |||
'@typescript-eslint/no-var-requires': 'off', | |||
'@typescript-eslint/ban-types': 'warn', | |||
'@typescript-eslint/no-require-imports': 'off', | |||
'@typescript-eslint/no-empty-object-type': 'off', |
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 have turned this off just for the moment. It will be turned back on once I follow up with a PR to update the framework side config.
@@ -154,7 +154,8 @@ module.exports = { | |||
// 'recommended' rules we alter | |||
'@typescript-eslint/no-explicit-any': 'warn', | |||
'@typescript-eslint/no-var-requires': 'off', | |||
'@typescript-eslint/ban-types': 'warn', | |||
'@typescript-eslint/no-require-imports': 'off', |
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.
The no-var-requires
above is now deprecated in favour of this rule. I have left the original in for the moment and matched it's level.
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.
Didn't spot anything that's worrying here! I like the idea of splitting :)
…pload-link * 'main' of github.com:redwoodjs/redwood: chore(linting): Remove/fix references to non-existant files (redwoodjs#11245) chore(rsa): Use swc for parsing server actions (redwoodjs#11243) chore(lint): Remove override for 'unused-imports/no-unused-imports' (redwoodjs#11244) chore(linting): Separate out framework and user linting config (redwoodjs#11242) fix: Update default tsconfig options (target, module and moduleResolution) (redwoodjs#11170) chore(fixture): Update tailwind dep (redwoodjs#11241) chore(deps): bump fast-xml-parser from 4.4.0 to 4.4.1 (redwoodjs#11239) chore(rsc): Switch last remaining transform-server test to inline snapshot (redwoodjs#11240) chore: brought in typescript-eslint@v8 with stylistic preset (redwoodjs#10911) chore(deps): bump axios from 1.7.3 to 1.7.4 (redwoodjs#11237) docs(serverConfig): Remove server config option from TOML (redwoodjs#11236) fix(deps): update typescript-eslint monorepo to v8 (major) (redwoodjs#11235)
See: #11234.
This will change user facing linting rules. From the changes I have seen I don't believe there are any rule changes here that we would want to override beyond those I have included in the PR.
Note my intention after this PR goes in is to split the framework and user facing linting rules into different configs - no shared config. I would then look to do further updates to the framework config.