chore: Use @carbon/styles #1886
Closed
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
See upgrade guide here: https://carbondesignsystem.com/migrating/guide/develop As proposed in carbon-design-system#1881 we can now start adopting v11 styles and merge incremental changes and fixes onto `next/v11-styles` branch. I would propose to merge small steps onto this new branch and discuss separte topics individually. This allows many contributors to propose small changes. The v11 style adoption should be held as minimal as possible since many components already have some notable changes in Carbon v11.
24 tasks
|
It seems that we can take larger steps. See #1881 |
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.
See upgrade guide here: https://carbondesignsystem.com/migrating/guide/develop
As proposed in #1881 we can now start adopting v11 styles and merge incremental changes and fixes onto
next/v11-stylesbranch. I would propose to merge small steps onto this new branch and discuss separte topics individually. This allows many contributors to propose small changes.The v11 style adoption should be held as minimal as possible since many components already have some notable changes in Carbon v11.