-
-
Notifications
You must be signed in to change notification settings - Fork 668
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
feat(core/ethereum): new ETH contract flow #4270
Conversation
2d720de
to
793bde7
Compare
|
Thanks. The fourth screen looks a bit different. Please add two line bottom part. And maybe shorten the amount of data displayed on the screen. cc @lapohoda How do the screen in the menu with data looks like? Can you please run the CI in different languages? Does the text fit everywhere? How about TS3? |
66fc602
to
39f7298
Compare
18d1c7e
to
069a2c0
Compare
|
0856612
to
020bf4e
Compare
24d8f0d
to
1683e06
Compare
1683e06
to
b5df4f2
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.
The flow looks nice on the example provided:
trezorctl ethereum sign-tx -n "m/44'/60'/0'/0/0" -d a9059cbb000000000000000000000000574bbb36871ba6b78e27f4b4dcfb76ea0091880b0000000000000000000000000000000000000000000000000000000000000123 -g 100 -G 100 -i 1 0xfc6b5d6af8a13258f7cbd0d39e11b35e01a32f93 0
However, the simple transfer
is now modified and I'm not sure it's what we want. See a comment below.
Also, from the point of view of a reviewer, I suggest splitting the PR into more logical commits which would ease the review.
For example, a decision on improving of the confirm_action
by introducing ConfirmActionMenu
and ConfirmActionStrings
should be done by two separate commits. You can always squash later.
d79537a
to
0d8f92f
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.
In general, I think we should go for more specialized rust/python functions rather than extending the existing functions with more arguments but I don't want to block the PR over this.
And as discussed in the past, updating fixtures.json
before the review makes it difficult to review the UI changes locally :(
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.
Did not test but code-wise I do not see any problem 👍
Please don't forget to include fixtures for translations.
d21e844
to
b283a4f
Compare
@@ -388,7 +417,9 @@ extern "C" fn new_confirm_properties(n_args: usize, args: *const Obj, kwargs: *m | |||
paragraphs.into_paragraphs(), | |||
TR::buttons__confirm.into(), | |||
None, | |||
false, |
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.
Rebase on main
might cause conflict here, should be easy to resolve.
e79201b
to
fd30397
Compare
fd30397
to
aa4365e
Compare
QA OK tested via:
Info:
|
PS: I know that this is different from Figma, where there is a shorter version of this string in TS3 / TT. I took a shortcut and have just one string in all models. I will add the shorter version and this will be fixed. Just FYI. IMO it is not a show stopper. @Hannsek |
Right, please create an issue for the fix and link it here. 🙏🏻 |
Fixes #4251