-
Notifications
You must be signed in to change notification settings - Fork 985
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
fix: non supported network warning is shown on the bridge flow #20098
Conversation
Jenkins BuildsClick to see older builds (32)
|
7bf2970
to
17be57b
Compare
[quo/network-list | ||
{:label (name network-name) | ||
{:theme theme |
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.
we don't need to pass theme this way. The provider does it.
The problem in that component is the schema was not updated to remove it.
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.
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.
Nice, the solely purpose of adding this change was to remove schema errors. I'll remove this and update the schema then
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.
yep for sure, but just as an FYI passing theme as a prop will actually do nothing because the component gets it from the context provider.
you'll have to remove in the respective component test too 👍
token-networks (network-utils/network-list token networks) | ||
token-networks-ids (mapv #(:chain-id %) token-networks) | ||
token-networks-ids-set (set token-networks-ids) | ||
token-available-on-network? (contains? token-networks-ids-set chain-id)] |
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.
do you really need token-networks
, token-networks-ids
, token-networks-ids-set
?
seems like this should all be done in the sub for token-available-on-network?
??
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.
or at least a util for that 🤔
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.
imo the let binding should just include the minimal data needed by the view's props. Other data can be taken out to utils or subs
Also this can help with allowing us to write tests for the underlying logic that prepares the props
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.
Yep, simplified the approach
17be57b
to
7bd7278
Compare
token-not-supported-in-receiver-networks? (and (not= tx-type :tx/bridge) | ||
(every? #(= (:type %) :not-available) | ||
(filter #(not= (:type %) :add) | ||
receiver-network-values))) |
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 that every
and filter
operation can be simplified with threading for readability. What do you think?
token-not-supported-in-receiver-networks? (and (not= tx-type :tx/bridge)
(->> receiver-network-values
(remove #(= (:type %) :add))
(every? #(= (:type %) :not-available))))
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.
Thanks for the suggestion, updated!
5f258ca
to
6d88b52
Compare
83% of end-end tests have passed
Failed tests (8)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Class TestWalletMultipleDevice:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestWalletOneDevice:
Expected to fail tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Passed tests (43)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestDeepLinksOneDevice:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
6d88b52
to
c7cf202
Compare
2093d44
to
c0f02be
Compare
Hey @briansztamfater, thanks for the fix! ISSUE 1: Cursor disappears from the amount field when you start typingIt appears again if you set the focus on the field by tapping it Steps:
Actual result (PR): video_2024-05-24_15-51-57.mp4Expected result (nightly): kekkekeke.mp4 |
Hey @qoqobolo thanks for testing! Does that only happens on Android or also on iOS? |
@briansztamfater Should we open an issue instead? seems this input has been changed and now is having problems |
Actually, I was able to reproduce it on develop on iOS Simulator. I think this was introduced after merging #20099. Can you please check @qoqobolo? If it a new issue, yes, we should log it and work on it separately @ulisesmac cc @J-Son89 |
@briansztamfater yep, I can see this issue now on today's nightly, will log it separately. |
96c9eae
to
08dac03
Compare
Signed-off-by: Brian Sztamfater <brian@status.im>
08dac03
to
823ff32
Compare
fixes #20080
Summary
This PR fixes warning about non supported networks being shown in the bridge flow, and disables unavailable networks for token in the
Bridge token to
screen.Platforms
Areas that maybe impacted
Functional
Steps to test
status: ready