Skip to content
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 json rpc engine #1872

Merged
merged 204 commits into from
Oct 19, 2023
Merged

Migrate json rpc engine #1872

merged 204 commits into from
Oct 19, 2023

Conversation

kanthesha
Copy link
Contributor

@kanthesha kanthesha commented Oct 19, 2023

Explanation

We would like to migrate most MetaMask libraries into core monorepo to make them easier to maintain.

In this PR, we are migrating json-rpc-engine into core monorepo. In the process of migration, we don't want to remove / loose the original GIT history, but to preserve the history of the library as though the entire project had been located in a merged-packages/json-rpc-engine directory all along.

We chose to place json-rpc-engine initially in the merged-packages and not packages so we can hide it from Yarn, ESLint, Prettier, and TypeScript. This allows us to clean it up and conform it to how we've configured this repo before we properly incorporate it.

References

Changelog

@metamask/json-rpc-engine

  • Migration: migrating json-rpc-engine to core monorepo

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've highlighted breaking changes using the "BREAKING" category above as appropriate

@socket-security
Copy link

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
eslint-config-prettier 8.8.0 None +14 6.04 MB lydell
jest 29.7.0 None +105 18 MB simenb
rimraf 5.0.5 filesystem, environment +2 1.43 MB isaacs
prettier-plugin-packagejson 2.4.3 None +8 11.4 MB matzkoh
ts-jest 29.1.1 None +106 18.3 MB kul
@types/jest 29.5.6 eval +19 4.91 MB types
@typescript-eslint/eslint-plugin 5.58.0 None +24 10.6 MB jameshenry
@typescript-eslint/parser 5.58.0 None +19 7.51 MB jameshenry
@types/node 18.18.6 None +0 3.8 MB types
depcheck 1.4.3 None +28 15.4 MB rumpl
prettier 2.8.7 None +0 11.2 MB prettier-bot
eslint 8.38.0 None +13 6.02 MB eslintbot
eslint-plugin-import 2.27.5 None +37 9.59 MB ljharb
typedoc 0.24.1 None +2 9.92 MB typedoc-bot
eslint-plugin-jest 27.2.1 None +25 10.9 MB simenb

@socket-security
Copy link

socket-security bot commented Oct 19, 2023

👍 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: [email protected], [email protected], @npmcli/[email protected], @npmcli/[email protected]

Next steps

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

@kanthesha kanthesha marked this pull request as ready for review October 19, 2023 18:29
@kanthesha kanthesha requested a review from a team as a code owner October 19, 2023 18:29
Copy link
Contributor

@MajorLift MajorLift left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good with clean history tree.

Screenshot 2023-10-19 at 12 01 04 PM

@MajorLift
Copy link
Contributor

@SocketSecurity ignore-all

@mcmire mcmire merged commit 59b1cdb into main Oct 19, 2023
@mcmire mcmire deleted the migrate-json-rpc-engine branch October 19, 2023 20:48
@kanthesha kanthesha mentioned this pull request Oct 20, 2023
3 tasks
georgewrmarshall added a commit to MetaMask/metamask-design-system that referenced this pull request Nov 12, 2024
…rocess (#100)

Duplicate of #92
with updated `main` branch

## **Description**

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](https://github.com/MetaMask/metamask-design-system/blob/main/docs/package-migration-process-guide.md#pr6-1-migrate-the-source-repos-git-history-into-the-merged-packages-temporary-directory-in-metamask-design-system).
This step migrates the Git history of the `design-tokens` repository
into the `metamask-design-system` monorepo, placing all contents under
the `merged-packages/design-tokens` directory.

[Example PR](MetaMask/core#1872) in core

## **Related issues**

Partly fixes:
#88

## **Manual testing steps**

1. Check the contents under `merged-packages/design-tokens` in the
`metamask-design-system` repository to ensure the file structure aligns
with the original `design-tokens` repository.
2. Verify that the commit history within `merged-packages/design-tokens`
accurately preserves previous `design-tokens` commits.
3. Confirm successful integration within the monorepo and that no errors
are introduced.

## **Pre-merge author checklist**

- [x] Verified `git-filter-repo` installation and migration process.
- [x] Confirmed all `design-tokens` files are correctly moved to
`merged-packages/design-tokens`.
- [x] Checked that the full commit history for `design-tokens` is
retained.
- [x] Followed MetaMask Coding Standards.
- [x] Set PR status appropriately.

## **Pre-merge reviewer checklist**

- [ ] Confirmed that all `design-tokens` files appear in
`merged-packages/design-tokens` with the correct structure.
- [ ] Verified the commit history for `design-tokens` is intact and
accurately reflects the original repository.
- [ ] Ensured this PR meets all acceptance criteria.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Merge json-rpc-engine history into merged-packages