-
Notifications
You must be signed in to change notification settings - Fork 2.9k
chore: migrate v9 packages to use eslint flat configs #35418
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
chore: migrate v9 packages to use eslint flat configs #35418
Conversation
eca3be2 to
7d548f5
Compare
📊 Bundle size reportUnchanged fixtures
|
4716d92 to
5897acd
Compare
|
Pull request demo site: URL |
change/@fluentui-babel-preset-global-context-705679a5-80b4-48f7-bb30-1a11814f14da.json
Show resolved
Hide resolved
5897acd to
7d55897
Compare
packages/react-components/component-selector-preview/stories/package.json
Outdated
Show resolved
Hide resolved
57e4027 to
0971f0d
Compare
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.
Great job, but few things need to be clarified/addressed before merge:
- not all
eslint.config.jshave rules from.eslintrc.json- is this intentional? - I don't get why we need lint script in package.json, couldn't we tweak the nx-executor instead?
packages/react-components/babel-preset-global-context/eslint.config.js
Outdated
Show resolved
Hide resolved
0971f0d to
13fbefb
Compare
Since this is temporary, I’m leaning toward keeping the logic in the npm scripts while we migrate all repos to flat ESLint configs and continue using the default target command. Later, we can update the workspace plugin to support only the new format. I tried updating it now to run different ESLint commands based on a condition, and that works, but it conflicts with the targetDefaults.lint command. Also, not all apps/packages are covered by the workspace plugin yet. So if I remove the default lint target and rely only on package-level lint scripts, it will work for the v9 packages, but since some packages don’t have their own lint script and there’s no default target anymore - we might lose lint coverage for some packages. 🤔 "apps/rit-tests-v9/*",
"apps/rit-tests-v8/*",
"tools/**/*",
"scripts/**/*",
"packages/eslint-plugin/**",
"packages/tokens/**",
"packages/react-conformance/**",
"packages/react-components/**/*",
"packages/charts/react-charts/**/*",
"packages/foundation-legacy/**",
"packages/jest-serializer-merge-styles/**",
"packages/react/**",
"packages/react-cards/**",
"packages/react-hooks/**",
"packages/react-focus/**",
"packages/react-examples/**",
"packages/react-experiments/**",
"packages/react-window-provider/**",
"packages/react-icon-provider/**",
"packages/charts/react-charting/**",
"packages/utilities/**",
"packages/react-icons-mdl2/**",
"packages/react-monaco-editor/**",
"packages/react-docsite-components/**",
"packages/react-file-type-icons/** |
13fbefb to
38e2c60
Compare
38e2c60 to
23dacd9
Compare
37a6a25 to
6abd22b
Compare
…ppropriate eslint cmd
8609d48 to
f639dca
Compare



This pull request updates multiple Fluent UI packages by migrating their linting configuration to use the new ESLint flat config format
workspace generator
create-packagewill be updated in a follow-up PRpartially implements #32289