feat(ramps): adds a controller method for fetching ramps tokens #7607
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.
Explanation
Adds a getTokens method to the ramps-controller. Currently, tokens are fetched in the mobile app via useRampTokens, which duplicates API logic and doesn't persist data. The new method centralizes token fetching in the controller, caches results, and stores tokens in controller state for persistence. This aligns token fetching with other ramps data (countries, eligibility) and prepares for mobile app integration in a follow-up PR.
References
https://consensyssoftware.atlassian.net/browse/TRAM-3018
Checklist
Note
Adds centralized token fetching and state in the ramps controller.
RampsController.getTokens(region?, action='buy')with request caching; normalizes region for cache keys; usesuserRegionwhen omitted; persiststokensin stateinit()now fetches user region, eligibility, then prefetches tokens;tokenscleared whenuserRegionchanges or eligibility fetch failsRampsService:getTokens; addsRampsToken/TokensResponsetypes andRampsService#getTokensWritten by Cursor Bugbot for commit d7c92ce. This will update automatically on new commits. Configure here.