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

[TokenRatesController] - Keep addresses in checksum format #4377

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

bergeron
Copy link
Contributor

@bergeron bergeron commented Jun 6, 2024

Explanation

When adding market data for tokens in #4206, it also changed the token addresses to be lowercased instead of checksum. This PR moves it back to the checksum format, since some places on the client expected it.

References

Changelog

@metamask/assets-controllers

  • CHANGED: Token rates controller uses checksum instead of lowercase format for token addresses

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

@bergeron bergeron requested a review from a team as a code owner June 6, 2024 06:42
@bergeron bergeron changed the title keep token addresses checksummed [TokenRatesController] - Keep addresses in checksum format Jun 6, 2024
@bergeron bergeron merged commit 9f3498a into main Jun 6, 2024
113 checks passed
@bergeron bergeron deleted the brian/checksum-token-addresses branch June 6, 2024 15:20
bergeron added a commit to MetaMask/metamask-extension that referenced this pull request Jun 6, 2024
## **Description**

Patches MetaMask/core#4377 to keep addresses in
the token rates controller in checksum format instead of lowercase,
since some places in extension expect it.


![image](https://github.com/MetaMask/metamask-extension/assets/3500406/ba9643a7-e4c3-4954-9af9-de23017ebf7a)


[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/25087?quickstart=1)

## **Related issues**



## **Manual testing steps**


## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
rekmarks pushed a commit to MetaMask/metamask-extension that referenced this pull request Jun 7, 2024
## **Description**

Patches MetaMask/core#4377 to keep addresses in
the token rates controller in checksum format instead of lowercase,
since some places in extension expect it.


![image](https://github.com/MetaMask/metamask-extension/assets/3500406/ba9643a7-e4c3-4954-9af9-de23017ebf7a)


[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/25087?quickstart=1)

## **Related issues**



## **Manual testing steps**


## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants