feat: Add Multichain API to @metamask/multichain
#4813
Draft
Commits on Oct 10, 2024
Commits on Oct 11, 2024
-
fix: typescript + linting (#4788)
## Explanation This PR fixes a lot of the linting and typescript errors. still some left but this covers a lot of it. <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes --------- Co-authored-by: Jiexi Luan <[email protected]>
-
Added exports for multichain package (#4789)
## Explanation <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> Added ESM exports for multichain package ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
-
-
-
Commits on Oct 14, 2024
Commits on Oct 15, 2024
-
-
-
-
-
-
-
-
-
-
-
Added handler wrappers to better integrate with existing middleware (#…
…4796) Add handler wrappers to better integrate with existing middleware in extension --------- Co-authored-by: Jiexi Luan <[email protected]>
-
Commits on Oct 16, 2024
-
-
Jl/caip multichain/update scope object account types (#4803)
## Explanation * Make `accounts` required on `ScopeObject` * Make `flattenScope` also add empty `accounts` array if missing * Rename `flattenScope` to `normalizeScope` * Rename `validateAndFlattenScopes` to `validateAndNormalizeScopes` * Rename `flattenMergeScopes` to `normalizeAndMergeScopes` ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
Commits on Oct 17, 2024
-
-
-
-
-
-
-
-
-
-
-
-
Update packages/controller-utils/src/util.test.ts
Co-authored-by: Mark Stacey <[email protected]>
-
Merge branch 'controller-utils-isEqualCaseInsensitive' into initializ…
…e-caip-multichain
-
add account support check in validator (#4816)
## Explanation Mirrors the [wallet_createSession handler ](https://github.com/MetaMask/metamask-extension/pull/27782/files#diff-107459889087f2776c6db636bd45498bef6749302f9d2dc633b4de17fede40a3R96-R108) in how eth account support is checked/asserted. Opted to do this rather than modify `assertScopeSupported` because the `bucketScopes` helper also relies on `assertScopedSupported` but doesn't care about accounts (which is why eth accounts are checked outside of assertScopeSupported in the wallet_createSession handler currently) ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes --------- Co-authored-by: Alex Donesky <[email protected]>
-
Commits on Oct 21, 2024
-
-
-
-
-
Revert "remove caip-permission-adapter-middleware"
This reverts commit fad338d.
-
-
-
Revert "remove caip-permission-adapter-middleware from exports"
This reverts commit c5980c6.
-
-
-
Revert "remove types/@metamask/eth-json-rpc-filters.d.ts"
This reverts commit a7a8e6e.
-
-
-
-
-
Commits on Oct 22, 2024
-
-
-
-
-
-
-
Loosen get adapter param types (#4835)
## Explanation Loosen `getEthAccounts` and `getPermittedEthChainIds` param type ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
-
Commits on Oct 23, 2024
-
-
-
-
-
Remove accountsChanged and chainChanged from KnownNotifications (sinc…
…e they are implicitly granted now)
-
Commits on Oct 24, 2024
-
Update packages/multichain/src/scope/transform.test.ts
Co-authored-by: Elliot Winkler <[email protected]>
-
-
Commits on Nov 21, 2024
-
Merge branch 'main' into caip-multichain-api
# Conflicts: # packages/multichain/package.json # packages/multichain/src/adapters/caip-permission-adapter-eth-accounts.test.ts # packages/multichain/src/adapters/caip-permission-adapter-eth-accounts.ts # packages/multichain/src/adapters/caip-permission-adapter-permittedChains.test.ts # packages/multichain/src/adapters/caip-permission-adapter-permittedChains.ts # packages/multichain/src/caip25Permission.test.ts # packages/multichain/src/caip25Permission.ts # packages/multichain/src/index.test.ts # packages/multichain/src/index.ts # packages/multichain/src/scope/assert.test.ts # packages/multichain/src/scope/assert.ts # packages/multichain/src/scope/authorization.test.ts # packages/multichain/src/scope/authorization.ts # packages/multichain/src/scope/constants.ts # packages/multichain/src/scope/supported.test.ts # packages/multichain/src/scope/supported.ts # packages/multichain/src/scope/transform.test.ts # packages/multichain/src/scope/transform.ts # packages/multichain/src/scope/types.ts # packages/multichain/src/scope/validation.test.ts # packages/multichain/src/scope/validation.ts # yarn.lock
-
-
-
-
CAIP Multichain API with permission refactor changes (#4961)
## Explanation ~~This diff is a bit messy since it also brings in the [core PR that refactors the CAIP-25 permission](#4950) which the [caip-multichain-api](https://github.com/MetaMask/core/tree/caip-multichain-api) branch doesn't have yet.~~ The main thing this PR does is adds `getSessionScopes()` which massages the new CAIP-25 permission into a `NormalizedScopesObject` ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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 - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes --------- Co-authored-by: Alex Donesky <[email protected]>
-
-
Caip multichain api normalized to internal (#4964)
## Explanation * Add getInternalScopesObject * Export getInternalScopesObject and getSessionScopes --------- Co-authored-by: Alex Donesky <[email protected]>
Commits on Nov 22, 2024
Commits on Nov 25, 2024
Commits on Nov 26, 2024
-
this seems like a reasonable tweak (#4980)
Not sure if I'm missing something about why we were refetching the middleware after passing in the whole entry...?
-
-
-
-
-
Commits on Nov 27, 2024
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.