chore: move design-tokens into merged-packages as part of migration process#100
Conversation
Pushing new tokens from Figma
…kens into feature/4-setup-ds-repository
Feature/4 setup ds repository
* Add issue template * Prettify issue template
* Adding css stylesheet contaiing color design tokens * Adding css path to build Co-authored-by: Cal Leung <cleun007@gmail.com>
* Updating some token descriptions that were wrong * Adding HEX values to descriptions and updating primary in dark mode * Updating token descriptions for brand colors * Adding secondary tokens to light theme * Adding storybook and adding initial design token documentation * Clean up * Updating some linting issues * Updating scripts * Adding secondary colors to dark and updating muted for both light and dark * Updating all muted values * Adding storybook and adding initial design token documentation * Clean up * Updating some linting issues * Updating all muted values * Swapping background default and alternative in dark mode and updating border color to be slightly less darker * Skip lib check * Add license to package.json * Updates to tokens and docs * Restoring token json token from main * Try to fix test but updating text * Fix build error Co-authored-by: Cal Leung <cleun007@gmail.com>
* updated dark-theme to hex (w alpha) * Update src/figma/tokens.json * Update src/figma/tokens.json * Update src/figma/tokens.json * Update src/figma/tokens.json * Update src/figma/tokens.json * Update src/figma/tokens.json * updated light-theme to hex (w alpha) * updated blue400 to correct hex * Changed all color to HEX value * Converting CSS variables * Generating light theme hex value updates * generating js dark theme tokens * Generating dark css * Fixing secondary default * Fixing border default description Co-authored-by: Hiro M <55973039+Akatori-Design@users.noreply.github.com>
* chore: upgrading storybook to 8.1.3 * chore: upgrading storybook to v8.1.4
* chore: updated css variables based on updated json * refactor: updated css variable namings * feat: added deprecated css files * refactor: updated migration changelist based on comments * refactor: updated migration doc * refactor: updated title for css part in migration doc * refactor: simplified deprecated tokens * refactor: removed deprecated colors and updated migration doc * refactor: updated css naming * refactor: nit changes * feat: readded overlay inverse back to css variables * docs: updating migrations doc layout * chore: reverting css import order --------- Co-authored-by: georgewrmarshall <george.marshall@consensys.net>
* feat: updated js tokens based on updated json * refactor: updated migration doc * feat: added deprecated tokens * refactor: removed deprecated tokens and updated tests * refactor: updated migration doc * refactor: removed addition language in migration doc * feat: readded overlay inverse back in js tokens * docs: updating migration docs to include js updates * fix: adding removed heading back --------- Co-authored-by: georgewrmarshall <george.marshall@consensys.net>
… Token JSON (#719) * feat: added tests for css variables * refactor: removed lint ignore
* feat: add dark classname * add light class
* chore: aligning dependencies with the metamask-design-system * chore: aligning dependencies with design-system-react
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
|
@SocketSecurity ignore-all
|
|
Performed the same checks that @MajorLift did in #92 (review).
|
|
Once again just as a reminder make sure to press the dropdown next to the green button and select "Create a merge commit" :) |
12 participants
Duplicate of #92 with updated
mainbranchDescription
This PR follows [PR#6] 1. Migrate the source repo's git history into the merged-packages/ temporary directory in metamask design system as part of the package migration process guide. This step migrates the Git history of the
design-tokensrepository into themetamask-design-systemmonorepo, placing all contents under themerged-packages/design-tokensdirectory.Example PR in core
Related issues
Partly fixes: #88
Manual testing steps
merged-packages/design-tokensin themetamask-design-systemrepository to ensure the file structure aligns with the originaldesign-tokensrepository.merged-packages/design-tokensaccurately preserves previousdesign-tokenscommits.Pre-merge author checklist
git-filter-repoinstallation and migration process.design-tokensfiles are correctly moved tomerged-packages/design-tokens.design-tokensis retained.Pre-merge reviewer checklist
design-tokensfiles appear inmerged-packages/design-tokenswith the correct structure.design-tokensis intact and accurately reflects the original repository.