-
Notifications
You must be signed in to change notification settings - Fork 25
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
Investigate viability of component level tokens #2162
Investigate viability of component level tokens #2162
Comments
Re-opening as there's one more PR attached to this |
🎉 This issue has been resolved in version 1.17.0-alpha.119 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.28.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 5.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…dispatch onChange event
…dispatch onChange event
🎉 This issue has been resolved in version 1.17.0-alpha.120 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 5.0.0-alpha.12 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0-alpha.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Acceptance Criteria:
Demo link: DemoApp
Source code: CSS file
React files
- Callout
- Table
- Accordion
- Container
- Button token
- Side Menu
Once component is chosen, create the necessary component level tokens to match the figma design parameters
Review component with updated token values with @twjeffery to verify fidelity to Figma design
Plan to do the below:
design-tokens
repo.ui-components
components with those new design token variables added on the step 1::root
CSS style to override new design token variables on step 1 and 2, with PP team values (color, border..) then deploy to review together with @twjefferyMarkup io feedback link
The text was updated successfully, but these errors were encountered: