Repository navigation
[pull] main from MetaMask:main - #244
Merged
Merged
Conversation
## Explanation Creates a new function to fetch trending tokens. The function accepts an array of CAIP chainIds along with other optional filtering query params. ## 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 --> ## 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 communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs), highlighting breaking changes as necessary - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Adds `getTrendingTokens` to fetch trending tokens by CAIP chain IDs with optional filters, exports it and new types, and updates tests and changelog. > > - **Token service (`src/token-service.ts`)**: > - Add `getTrendingTokens` with optional filters (`sortBy`, liquidity, volume, market cap) using new `getTrendingTokensURL`. > - Introduce types `SortTrendingBy` and `TrendingAsset`. > - **Exports (`src/index.ts`)**: > - Export `getTrendingTokens` and types `SortTrendingBy`, `TrendingAsset`. > - **Tests (`src/token-service.test.ts`)**: > - Add coverage for `getTrendingTokens` success/error/empty cases. > - **Docs**: > - Update `CHANGELOG.md` with new function and types. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit da456e8. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
## Explanation Minor release for `assets-controllers`. ## 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 --> ## 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 communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs), highlighting breaking changes as necessary - [ ] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Release assets-controllers 87.1.0 with trending tokens API and bump monorepo to 662.0.0; update dependent packages to use the new version. > > - **Packages**: > - `@metamask/assets-controllers` → `87.1.0` > - Added `getTrendingTokens` API and new types `SortTrendingBy`, `TrendingAsset` (changelog). > - Bump devDeps to `@metamask/assets-controllers@^87.1.0` in: > - `packages/bridge-controller/package.json` > - `packages/transaction-pay-controller/package.json` > - **Repo**: > - Monorepo version → `662.0.0` in root `package.json`. > - Update `packages/assets-controllers/CHANGELOG.md` links and `yarn.lock` entries accordingly. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8c30bb3. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )