-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[eslint-plugin] support Flat Config #29751
Conversation
TODO: - some rules cannot be configured yet in azure-sdk-customized.ts
Also - fix `files` patterns for ts files. - add better typing for configs. - disable eslint-plugin-import for now as it doesn't support flat config yet.
API change check API changes are not detected in this pull request. |
@@ -24,20 +24,27 @@ | |||
"bugs": { | |||
"url": "https://github.com/Azure/azure-sdk-for-js/issues" | |||
}, | |||
"main": "dist/index.js", | |||
"main": "dist-esm/src/index.js", | |||
"exports": { |
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.
We should be using tshy here to ensure we have proper types for CJS and ESM. Otherwise these are only types for ESM and not CJS
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 will fix this in a follow-up 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.
Looks good but needs fixup to be ESM/CJS via tshy
/check-enforcer override |
ESLint v9 drops support for legacy .eslintrc style configuration files. To move to v9 we need to migrate to the new Flat Config files. This PR adds support for Flat Config file and migrate cosmos and identity-broker packages to use the flat config. Legacy config files are still supported.
Some eslint plugins that we use don't support flat config yet so they are disabled.
Related issue: #29750