-
Notifications
You must be signed in to change notification settings - Fork 5
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
Create transaction screen and rework addresses screen #38
Conversation
Functional test looks good, couple comments:
|
Please do not change the context of the PR to include more than it needs to - please stack this PR with another to address changes to the addresses screen - there were other things to address in this PR before adding more to it |
I was not planning on exceeding the 1000 LOC (unofficial) limit. I did not rewrite history, so you can review the new changes I added separately from the previous ones. I can address all the review comments together. Does this create a problem for you? |
It's a configurable amount by the user, so we hide it. I don't see a reason not to, same as all other amounts. Do you have a strong argument against it?
What do you mean? As in "input field labels"? |
Yes, the scope of the PR is growing making it more complicated
I don't, but I also don't understand why it's useful to hide a fee amount which I'd like to. The purpose of a fee is to pay for network resources so what is sensitive about this?
I'll get you a picture, I don't know how else to describe it other than all the user owned addresses with labels aren't using their label on that view |
My little grain of salt regarding hiding the amounts : IMO, the only amounts that should be hidden are the holdings & read-only values (tx values in history for instance). |
I don't fully get the argument for the fees being visible in discreet mode, but since both of you support that I'll change it 👍 |
It did grow, but won't grow more than this 😇. It's 800 LOC and I think it's reasonable. I don't think I did something wrong, I asked for your review, you gave it, I pushed some new code ensuring it won't grow much, I asked for it again. Is that something we don't want to do in the future? We agreed that we shouldn't rewrite history so that people can review newly added commits. Which I respected. Would you have said the same it I only asked for your review once after pushing the new code? If you don't feel like reviewing it, I can pass it to @mvaivre. I won't split it, it creates overhead. |
Ah, you mean address labels. The Transfers screen is not in the scope of this PR. It's also not properly represented in the mockups. |
I am changing the status of this PR to WIP. I cannot mark it as "Draft" otherwise, and I cannot remove reviewers either. |
As of today, I actually think that specifying the addresses' labels in the "global" TX list view is not a vital information. I'd like to start without it, try the UI, and iterate if necessary :) |
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.
Damn that carousel is nice to have ✨ Code looks good!
On the functional test I noticed one thing in particular: if you press on an address card and go back, the copy and qr code buttons remain disabled.
Screen_Recording_20220822-073107_mobile-wallet.mp4
Two minor things I noticed: it's not obvious when pressing "copy address" that the operation succeeded, and when the QR code modal appears it's not obvious how to close it (other than people's natural reaction to just hit the screen to see what happens)
Nice catch @LeeAlephium , thanks for the thorough tests!
I'll install a toast message lib because only Android supports it natively 👎 And then @mvaivre can re-iterate on it to improve its styling, since there's nothing in the mockups for notifications atm.
The QR code modal is really as basic as I could make it cause I wanna wait for @mvaivre to design one first, so that I don't waste time. I only wanted to make it functional for now. But thanks for the feedback! |
src/components/Amount.tsx
Outdated
fullPrecision = false, | ||
prefix, | ||
suffix = '', | ||
hideOnDiscreetMode = true, |
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.
Could we rename this to showAlways
? It makes logical statements easier to reason about: if (!discreetMode || !hideOnDiscreetMode) {
vs if (!discreetMode || showAlways) {
. The former is like 3 negatives 🙃 "or if not not showing on not showing amounts mode" .... 😆 Just make sure that the change includes showAlways = 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.
I'll rename it to showOnDiscreetMode
:)
Functional tests look good 👍 My remaining comments are not necessary |
No description provided.