Closed alexandremgo closed 2 years ago
Thanks for your contribution. To be able to merge in develop branch, you need to:
/generate-screenshots
[ ] if needed, /upgrade-llc
If your PR contains UI related changes, it might be necessary to regenerate screenshots.
If your PR requires an update to the ledger-live-common library,
once the PR is merged on develop on ledger-live-common side,
you need to run /upgrade-llc
to switch back to ledger-live-common@develop here before merging.
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π΄ | Statements | 8.74% | 9/103 |
π΄ | Branches | 0% | 0/19 |
π΄ | Functions | 2.94% | 1/34 |
π΄ | Lines | 8.33% | 8/96 |
Report generated by π§ͺjest coverage report action from 3ed7e504846375dc82521c53bb05238f7639391e
π¦ Context (issues, jira)
LIVE-1317
The "something else" choice redirects to the end of the usb-troubleshooting flow
Add to adapt a bit compared to the given design (from figma): the Nano S repair modal is old and has not been updated to the new troubleshooting screens.
π» Description / Demo (image or video)
Video: new feature
https://user-images.githubusercontent.com/15096913/163337621-789599a3-3066-4cf5-ab43-f8fe0d16d1ec.mp4Video: the other repair modal screens are not broken
https://user-images.githubusercontent.com/15096913/163339871-774ec649-5b2c-4929-b752-bc429613c3e8.mp4π€ Expectations to reach