generated from MetaMask/metamask-module-template
-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
migrate design tokens: Replace config files #106
Labels
Comments
This was referenced Nov 13, 2024
georgewrmarshall
added a commit
that referenced
this issue
Nov 14, 2024
## **Description** This PR resolves [Issue #106](#106) by updating the configuration files as part of the design tokens migration process. Following the [Package Migration Process Guide](https://github.com/MetaMask/metamask-design-system/blob/main/docs/package-migration-process-guide.md#pr9-5-replace-config-files) ## **Related issues** Fixes: #106 ## **Manual testing steps** 1. Verify that the updated config files match the steps in the migration guide ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) - [x] I've completed the PR template to the best of my ability. - [x] I’ve included tests if applicable. - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable. - [x] I’ve applied the appropriate labels to the PR. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g., pulled and built the branch, checked the app, and verified updated configurations). - [ ] I confirm that this PR addresses all acceptance criteria described in issue #106 and includes necessary testing evidence such as recordings or screenshots.
georgewrmarshall
added a commit
that referenced
this issue
Nov 15, 2024
…okens (#115) ## **Description** This PR resolves [Issue #108](#108) by aligning the dependencies and build scripts in the target package with the monorepo's root configuration as part of the design tokens migration process. Following the [Package Migration Process Guide](https://github.com/MetaMask/metamask-design-system/blob/main/docs/package-migration-process-guide.md#pr10-6-align-dependencies-and-build-scripts-with-monorepo) ## **Related issues** Fixes: #108 ## **Manual testing steps** 1. Verify that all unnecessary dependencies have been removed ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) - [x] I've completed the PR template to the best of my ability. - [x] I’ve included tests if applicable. - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable. - [x] I’ve applied the appropriate labels to the PR. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g., pulled and built the branch, checked the app, and verified updated configurations). - [ ] I confirm that this PR addresses all acceptance criteria described in issue #106 and includes necessary testing evidence such as recordings or screenshots.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As part of the design tokens migration, this task focuses on updating configuration files to ensure consistency across the monorepo. Key config files in non-root directories should extend from the root directory’s corresponding files, aligning with the shared project standards. For additional guidance, refer to the Package Migration Process Guide.
Technical Details
tsconfig*.json
,typedoc.json
, andjest.config.js
to extend from the root directory versions.deepmerge
as adevDependency
for handling configuration merging.Acceptance Criteria
tsconfig*.json
,typedoc.json
,jest.config.js
) are set to extend from the root versions.deepmerge
is added as adevDependency
and applied as needed.References
The text was updated successfully, but these errors were encountered: