Closed
Description
openedon Aug 25, 2021
Part of #34284
Why
The new ColorPicker
should replace the legacy version of the component
What
This effectively means moving the code of the g2 component over to the src
folder of the @wordpress/components
package, completely replacing the legacy component.
We need to ensure that usages of the ColorPicker
keep working as expected, despite the changes.
A/C
- The new
ColorPicker
is promoted to thesrc
folder, replacing the legacy component (a legacy adapter has already been created in components: Add deprecated props adapter for ColorPicker #34014)- The code of the legacy
ColorPicker
is deleted
- The code of the legacy
- Asses any potential breaking change introduced
- Test that the component works as expected, in continuity with the previous version:
- In storybook
- In the usages across the Gutenberg repository
- Introduce a changelog entry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
WordPress component systemWordPress component system/packages/components/packages/componentsNew feature to highlight in changelogs.New feature to highlight in changelogs.