Skip to content

Fixed a duplicate account import test case relying on an upstream typo#16371

Closed
TimTinkers wants to merge 3 commits intoMetaMask:developfrom
TimTinkers:import-typo-fix
Closed

Fixed a duplicate account import test case relying on an upstream typo#16371
TimTinkers wants to merge 3 commits intoMetaMask:developfrom
TimTinkers:import-typo-fix

Conversation

@TimTinkers
Copy link
Copy Markdown

@TimTinkers TimTinkers commented Nov 3, 2022

Explanation

This pull request in the upstream KeyringController MetaMask/KeyringController#153 fixes the issue #16370.

This current pull request fixes a test case such that the upstream KeyringController fix can be used.

Currently, users encounter a typo when attempting to import a duplicate account into MetaMask. The typo is not localized and originates from the upstream KeyringController. I have submitted a pull request here MetaMask/KeyringController#153 to fix the typo, but doing so would break a test case in this repository which expects the typo. This pull request fixes the test case such that it will expect the typo-free error from KeyringController. This pull request should be merged after MetaMask/KeyringController#153 because it is dependent on the typo being fixed there.

More Information

I encountered this typo when attempting to import an account via its private key after that account had previously already been imported.

Screenshots/Screencaps

Before

before

After

The UI will look the same until after MetaMask/KeyringController#153 is merged and incorporated. After that point, the end user will no longer see the "you're are" typo and will just see "you are".

Manual Testing Steps

You can verify that this issue is present by importing an account from private key and then attempting to import the same account. You should no longer see the typo if using the new KeyringController.

Pre-Merge Checklist

  • PR template is filled out
  • IF this PR fixes a bug, a test that would have caught the bug has been added
  • PR is linked to the appropriate GitHub issue
  • PR has been added to the appropriate release Milestone

+ If there are functional changes:

  • Manual testing complete & passed
  • "Extension QA Board" label has been applied

@TimTinkers TimTinkers requested a review from a team as a code owner November 3, 2022 21:29
@TimTinkers TimTinkers requested a review from Gtonizuka November 3, 2022 21:29
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Nov 3, 2022

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@TimTinkers
Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@HowardBraham
Copy link
Copy Markdown
Contributor

This was merged with #15558

@github-actions github-actions bot locked and limited conversation to collaborators Dec 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants