forked from LedgerHQ/app-tezos-legacy
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use standard use cases #117
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spalmer25
force-pushed
the
palmer@functori@use-standard-useCases
branch
2 times, most recently
from
July 25, 2024 10:05
7ef9244
to
3698c97
Compare
This was
linked to
issues
Jul 25, 2024
black_screen snapshots remains from older version
In order to clarify the tests
spalmer25
force-pushed
the
palmer@functori@use-standard-useCases
branch
from
July 25, 2024 10:07
3698c97
to
70cf539
Compare
spalmer25
force-pushed
the
palmer@functori@use-standard-useCases
branch
from
July 25, 2024 13:01
70cf539
to
1524f28
Compare
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.
test_setup_context is failing.
ajinkyaraj-23
approved these changes
Jul 25, 2024
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.
LGTM
- nbgl_useCaseAddressReview instead of nbgl_useCaseAddressConfirmation - nbgl_useCaseReviewStatus instead of nbgl_useCaseStatus
- nbgl_useCaseReviewStart instead of nbgl_useCaseReviewLight and nbgl_useCaseStaticReviewLight - standard status message
- nbgl_useCaseGenericReview instead of nbgl_useCaseReviewStart The pre-defined review flows do not meet our expectations as they are built specifically for reviewing/signing transactions/messages and therefore the wording is defined for this. - standard status message
- nbgl_useCaseGenericReview instead of nbgl_useCaseReviewStart The pre-defined review flows do not meet our expectations as they are built specifically for reviewing/signing transactions/messages and therefore the wording is defined for this. - standard status message
- check_app_context: only check data and not the screens - goto_home_public_key: do not check chain_id - disable_hwm: do not check app_context
In order to move all parameter information to the end of the flow as required for useCaseHomeAndSettings
Instead of useCaseHome and nbgl_useCaseSettings
spalmer25
force-pushed
the
palmer@functori@use-standard-useCases
branch
from
July 26, 2024 09:04
33ebe57
to
c7c0f99
Compare
ajinkyaraj-23
approved these changes
Jul 26, 2024
spalmer25
force-pushed
the
palmer@functori@use-standard-useCases
branch
from
July 26, 2024 10:29
2629f24
to
9000f8b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.