-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat: cp-7.47.0 solana code fences #15297
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
Conversation
|
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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15297 +/- ##
==========================================
+ Coverage 68.46% 68.69% +0.23%
==========================================
Files 2372 2381 +9
Lines 51275 51432 +157
Branches 7634 7663 +29
==========================================
+ Hits 35103 35333 +230
+ Misses 13942 13853 -89
- Partials 2230 2246 +16 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This comment was marked as outdated.
This comment was marked as outdated.
|
|
NicolasMassart
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested (built the feature, provided screenshots in description) and I approve the changes, we just have to make sure the e2e failures are not related to this PR to merge.
QA team can help on this. Contact them please.
@Andepande is on it |
<!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** Got it! Here's an updated PR description that includes those details: --- Fixes existing smoke E2E test failures that occur when the Solana feature is enabled. * Suppresses the Solana feature sheet for tests that use fixtures. * For tests that don’t use fixtures, automatically swipes down to dismiss the modal. This ensures stability across smoke tests regardless of the Solana feature flag state. --- Let me know if you'd like to mention specific test files or tag reviewers. <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Related issues** Fixes: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1a3fd4be-4f11-42b7-a2a7-a6c8b14f399a ## **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 Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.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-mobile/blob/main/.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.
|
|
NicolasMassart
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve these e2e changes and addition of test ids in the UI



Description
Note
The
keyring-snapsis the code fence flag that allows for snaps like thesolana,bitcoin, any keyring snap to work, the Solana snap and bitcoin snap are keyring-snaps.This code fence has all the broad/general code for non-evm snaps, and then for specific network logic we have the solana, bitcoin etc...
Related issues
Fixes: the current feature is under code fencing, only available in our beta build, it has to be moved from beta to main set to be available in the next release.
Manual testing steps
Screenshots/Recordings
Before
Add account
Select network
After
New welcome bottom sheet
Add account
Select network
Pre-merge author checklist
Pre-merge reviewer checklist