-
Notifications
You must be signed in to change notification settings - Fork 984
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: select asset screen ui #17780
feat: select asset screen ui #17780
Conversation
Jenkins BuildsClick to see older builds (92)
|
dcd3498
to
1fae0c9
Compare
518df6e
to
2fdefba
Compare
63e9661
to
c9458bb
Compare
8009d9e
to
c26eed8
Compare
7ce159f
to
42eb3a0
Compare
@@ -85,7 +85,7 @@ | |||
:customization-color :blue}] | |||
[quo/wallet-graph {:time-frame :empty}] | |||
[quo/wallet-ctas | |||
{:send-action #(rf/dispatch [:open-modal :wallet-select-address]) | |||
{:send-action #(rf/dispatch [:open-modal :wallet-select-address (:address account)]) |
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.
should we make the params a map here?
:open-modal :wallet-select-address {:address (:address account)}
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.
Would be cleaner, agree. But BTW, wondering if we actually need to pass this in navigation params, or maybe would be a better idea to handle this in the app db with subs and events, because either way the user will be able to switch accounts while being inside the send flow
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.
yeah that's a fair point. We could also do as a follow up if it's too much effort here? 🤔
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 think it is not needed so I removed, we can create a follow up in case we need it later
@@ -41,70 +44,155 @@ | |||
:container-style style/empty-container-style}])) | |||
|
|||
(defn- address-input |
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.
can be done outside this pr, I believe we can make this a common component as the same component is used on watch-only select address screen too 👍
[tab-view @selected-tab]]))) | ||
(let [valid-ens-or-address? (boolean (rf/sub [:wallet/valid-ens-or-address?]))] | ||
[rn/scroll-view | ||
{:content-container-style (style/container margin-top) |
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.
can margin-top be achieve with insets true in the screens.cljs file?
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.
Can be replaced with SafeAreaView which should handle this automatically
{:content-container-style (style/container margin-top) | ||
:keyboard-should-persist-taps :handled | ||
:scroll-enabled false} | ||
[quo/page-nav |
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.
beyond this pr and beyond 1.27 priorities. seems we should eventually make this a common connected component for wallet with all of the functionality built in for wallet page nav. 👍
cc @smohamedjavid, @OmarBasem @ulisesmac @mmilad75
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.
created - #17872
(if (or @input-focused? (> (count @input-value) 0)) | ||
[rn/keyboard-avoiding-view | ||
{:style {:flex 1} | ||
:keyboard-vertical-offset 26} |
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.
where are you getting this 26
from? 🤔 anyway I think when we merge #17737 we can use this here instead 👍
Thanks @briansztamfater! |
73% of end-end tests have passed
Failed tests (8)Click to expandClass TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Expected to fail tests (4)Click to expandClass TestCommunityOneDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Passed tests (33)Click to expandClass TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityOneDeviceMerged:
|
75% of end-end tests have passed
Failed tests (2)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Passed tests (6)Click to expandClass TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMergedTwo:
|
8f0e4eb
to
21f3f1c
Compare
Hi @briansztamfater, thanks again for waiting! |
Signed-off-by: Brian Sztamfater <brian@status.im>
21f3f1c
to
af4ad5f
Compare
It is fine, we will do a design review later so we can skip this part for now. Thanks for testing! |
feat: select asset screen ui Signed-off-by: Brian Sztamfater <brian@status.im>
fixes #16914
Summary
This PR integrates asset selection page UI, using fetched data from status-go and filtering through search input
Platforms
Functional
Steps to test
status: ready