Closed lambertkevin closed 2 years ago
Thanks for your contribution. To be able to merge in develop branch, you need to:
/generate-screenshots
[x] 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 c951db99c5af8791dd69b0cceb0bd3a3956170ec
@gsoares-ledger adding you as reviewer just in case you have spare time ^^ as you're the only other NFT expert around.
Not for 2.41 branch, pending its merge into develop.
π¦ Context (issues, jira)
[LIVE-1899] [LIVE-1900] [LIVE-1903] [LIVE-1934]
π» Description / Demo (image or video)
https://user-images.githubusercontent.com/44363395/164739972-d41dff2d-91ac-41f8-b695-daff23e5f6b1.mov
https://user-images.githubusercontent.com/44363395/164740274-438fdf6d-1683-4df4-b3f4-5022947c1c9a.mov
https://user-images.githubusercontent.com/44363395/164740751-2b70cfe1-9b04-4b56-a317-f9836bed8272.mov
π€ Expectations to reach
PR must pass CI, rebase develop if conflicts. Thanks!