-
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
Quo - Wallet/Required-Tokens Component #18164
Conversation
Jenkins BuildsClick to see older builds (28)
|
57ef668
to
a67b190
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.
Nice work @ajayesivan ! :)
[react-native.core :as rn] | ||
[schema.core :as schema])) | ||
|
||
(def ?schema |
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.
@clauxx, @yqrashawn - can you take a look at the schema :)
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.
This is my first attempt at crafting a schema, and I welcome any feedback or suggestions!
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 we have any docs about usage of schema? and if we define schema do we still need to use docstring for components?
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.
Good point @mohsen-ghafouri - I think we should not use doc strings if using schemas
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.
That's a good point. I believe we can use the schema alone, which reduces maintenance overhead. IMO schemas are generally easier to keep up-to-date compared to docstrings.
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.
schema below LGTM
@@ -403,6 +404,7 @@ | |||
(def network-bridge quo.components.wallet.network-bridge.view/view) | |||
(def network-routing quo.components.wallet.network-routing.view/view) | |||
(def progress-bar quo.components.wallet.progress-bar.view/view) | |||
(def required-tokens quo.components.wallet.required-tokens.view/view) |
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 work, LGTM 🚀
a67b190
to
a7dd0f0
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.
Nice work! 🚀
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!!
a7dd0f0
to
6509e23
Compare
83% of end-end tests have passed
Failed tests (2)Click to expandClass TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Expected to fail tests (6)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Passed tests (40)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestDeepLinksOneDevice:
Class TestActivityMultipleDevicePR:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
|
Hi @Francesca-G, Could you please do a design review of this component? We are not yet using it in the UI, you can verify it in the Quo Preview. |
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.
Looks good ✨
Adding the follow up required label due to a minor issue in the token avatar and collectible size, see comment here
64fe9ac
to
0da1a89
Compare
@Francesca-G Thanks for the review! I have fixed the token & collectible size. |
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.
💯
0da1a89
to
2823276
Compare
2823276
to
affba3e
Compare
affba3e
to
ba9c3ea
Compare
@status-im/mobile-qa, could you kindly verify if the failed e2e tests are related to this PR? Additionally, since this PR introduces a new Quo component that is currently only used in the preview, should we consider manual testing? |
Hi @ajayesivan! Thank you for the PR.
Failed e2e are not PR related.
In this case manual QA can be skipped. So we this PR is ready for merge! |
fix #18139
Quo Preview -> Wallet -> Required Tokens
iOS Screenshots
Android Screenshots
status: ready