-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
migration: migrate converged packages to new DX (1st stage) #18579
Closed
32 tasks done
Labels
Milestone
Comments
2 tasks
This was referenced Jun 17, 2021
This was referenced Jun 18, 2021
msft-fluent-ui-bot
pushed a commit
that referenced
this issue
Jun 18, 2021
#### Pull request checklist - [x] Addresses an existing issue: partially implements #18579 - [x] Include a change request file using `$ yarn change` #### Description of changes - Migration of package to new DX - Conversion of styling from SASS to make-styles
msft-fluent-ui-bot
pushed a commit
that referenced
this issue
Jun 18, 2021
#### Pull request checklist - [x] Addresses an existing issue: Fixes part of #18579 - [x] Include a change request file using `$ yarn change` #### Description of changes - migrates the `react-divider` package to new DX using `nx workspace-generator migrate-converged-pkg`
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
2 tasks
msft-fluent-ui-bot
pushed a commit
that referenced
this issue
Jul 19, 2021
#### Pull request checklist - [x] Addresses an existing issue: Fixes part of #18579 - [x] Include a change request file using `$ yarn change` #### Description of changes - migrates `react-button` package using `yarn nx workspace-generator migrate-converged-pkg` - moved `Playground.tsx` and `Playground.types.tsx` to `react-button` package as they were deleted by migration script. - updates `useCompountButtonStyles` to explicitly declare `marginTop` value to fix babel-loader error. - extracted `buttonBaseProps` from `Button` story to its own file. - updated import paths for all Button stories.
This was referenced Jul 21, 2021
msft-fluent-ui-bot
pushed a commit
that referenced
this issue
Jul 21, 2021
2 tasks
PeterDraex
pushed a commit
to PeterDraex/fluentui
that referenced
this issue
Aug 6, 2021
#### Pull request checklist - [x] Addresses an existing issue: Fixes part of microsoft#18579 - [x] Include a change request file using `$ yarn change` #### Description of changes - migrates `react-button` package using `yarn nx workspace-generator migrate-converged-pkg` - moved `Playground.tsx` and `Playground.types.tsx` to `react-button` package as they were deleted by migration script. - updates `useCompountButtonStyles` to explicitly declare `marginTop` value to fix babel-loader error. - extracted `buttonBaseProps` from `Button` story to its own file. - updated import paths for all Button stories.
PeterDraex
pushed a commit
to PeterDraex/fluentui
that referenced
this issue
Aug 6, 2021
#### Pull request checklist - [x] Addresses an existing issue: Fixes partially microsoft#18579, fixes microsoft#19050 - [ ] Include a change request file using `$ yarn change` #### Description of changes Migration to new DX for react-card
all vNext and react-components suite has been migrated 🎉 excellent collaboration team ! |
This was referenced Aug 27, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Preparation:
What is new DX (1st stage) ?
tsconfig.base.json
, that uses TSpath aliasesjest-serializer-make-styles
andbabel-make-styles
needs still manual build node packages within repo are required to be built first before using (blocking no-build dev loop mode) #18357)storybook
andjest
binaries respectively/.storybook
configuration./jest.preset.js
./jest.config.js
which enables also easy debugging from within your IDE.Packages that need migration
How to migrate
yarn nx workspace-generator migrate-converged-pkg --name='@fluentui/<package-name>'
FAQ
Why should I migrate my own/teams packages instead of one person doing the whole migration for me?
As we are in process of introducing new Dev Experience for how to approach migrations in general within monorepo, that could be implemented also for customers in the future, we wanna:
I wanna create new package, how should I proceed ?
If you'll run into any issues while running the migration generator please open github issue.
Thank you and Happy migrating!
The text was updated successfully, but these errors were encountered: