You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
all work should be done in the feat/carbon-for-ibm-dotcom-v2 branch
This epic tracks the work to update all components in @carbon/ibmdotcom-web-components. Component styles and markup need to be updated as all upstream Carbon dependencies now use Carbon v11. As components in @carbon/web-components - an upstream dependency - have been upgraded to v11, the markup in many components in this package must be updated as well.
Issues with the v2 design change label have specific design requirements and may also introduce breaking changes. These issues should include updated design specs, component API changes, and may require working with the design team during implementation.
Note: Currently there is no standardization of tests, duplicate and/or redundant tests, and inconsistency in UI testing. The team consensus is to modify the tests as necessary (markup/name changes, etc) but to give this lower priority if it becomes a blocker in completing a particular component. The tests will get an overhaul in the future, so it is unnecessary to get them completely updated.
The content you are editing has changed. Please copy your edits and refresh the page.
Epic to track all component work for V2
Note
all work should be done in the
feat/carbon-for-ibm-dotcom-v2
branchThis epic tracks the work to update all components in
@carbon/ibmdotcom-web-components
. Component styles and markup need to be updated as all upstream Carbon dependencies now use Carbon v11. As components in@carbon/web-components
- an upstream dependency - have been upgraded to v11, the markup in many components in this package must be updated as well.Issues with the
v2 design change
label have specific design requirements and may also introduce breaking changes. These issues should include updated design specs, component API changes, and may require working with the design team during implementation.Component dependency map (Box Canvas)
Acceptance criteria
For all components, some basic acceptance criteria should be observed when working on them:
@carbon/ibmdotcom-web-components
v2 unit tests Epic #10369)Components
content-section
to v2 design specs #10454Deprecated Components
The text was updated successfully, but these errors were encountered: