docs(examples): add simple example of v10 and v11 being used together #12067
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for carbon-components-react ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for carbon-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
jnm2377
approved these changes
Sep 12, 2022
|
|
||
| ## Incremental migration | ||
|
|
||
| We ave recently released a new version, v11, of our component library and a |
There was a problem hiding this comment.
Suggested change
| We ave recently released a new version, v11, of our component library and a | |
| We have recently released a new version, v11, of our component library and a |
| common question we receive is if users can adopt v11 incrementally and the | ||
| answer is yes! If the burden of migrating to v11 is too big to take on all at | ||
| once, but there are features of our latest release you want to take advantage | ||
| of, it is likely that you can pull in just the parts yiu are wanting to use |
There was a problem hiding this comment.
Suggested change
| of, it is likely that you can pull in just the parts yiu are wanting to use | |
| of, it is likely that you can pull in just the parts you are wanting to use |
tay1orjones
approved these changes
Sep 13, 2022
| common question we receive is if users can adopt v11 incrementally and the | ||
| answer is yes! If the burden of migrating to v11 is too big to take on all at | ||
| once, but there are features of our latest release you want to take advantage | ||
| of, it is likely that you can pull in just the parts yiu are wanting to use |
There was a problem hiding this comment.
Suggested change
| of, it is likely that you can pull in just the parts yiu are wanting to use | |
| of, it is likely that you can pull in just the parts you are wanting to use |
tay1orjones
added
status: ready to merge 🎉
and removed
status: one more review 👀
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
REF #11986
REF #12051
This PR adds a simple example of v10 and v11 working together. Most of the components are v10 but it uses the new Stack component and the v11 StructuredList. It's super simple but I wanted to get something up quick that we could build on/add to
Changelog
New
Changed
Removed
Testing / Reviewing
Pull down PR and
yarnandyarn devthe/incremental-migrationexample, make sure it all looks okay.