-
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
List Items/Approval Info Component #20317
base: develop
Are you sure you want to change the base?
Conversation
Jenkins BuildsClick to see older builds (28)
|
2fa4591
to
aa7efcf
Compare
{:color (if blur? | ||
colors/white | ||
(colors/theme-colors colors/neutral-100 colors/white theme))}) | ||
|
||
(defn description | ||
[blur? theme] | ||
{:color (icon-description-color blur? 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.
hi @ajayesivan, Do we need another function for description color? We don't have one for label color.
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 icon-description-color
function is also used for icons. Let me know if the name is not clear enough, or if you have any other suggestions.
:color (style/icon-description-color blur? theme)}])] |
(cond | ||
(#{:spending-cap :token-contract :network | ||
:collectible} |
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 case will be better choice here. wdyt?
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.
It is way better with case
, thanks for the suggestions 😊
[text/text | ||
{:size :paragraph-1 | ||
:weight :semi-bold | ||
:style (style/label blur? theme)} label] |
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.
Quick one: There's at least another instance of this style problem in this namespace https://guide.clojure.style/#vertically-align-fn-args
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 this is something our linter should handle, no?
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.
@BalogunofAfrica, we would all love to get that automated, but it's a bit hard I think. I could try myself to configure this, but it's not trivial because we could easily introduce formatting side-effects in other parts of the code because we told zprint to respect newlines. Also for zprint, this is nothing more than a vector, so I think the solution could be to somehow tell it to detect if the second argument to a vector is a map and then try to fit it on the same line as the first element.
We could also try to consult with zprint's author.
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.
Fixed all of the formatting issues that I found.
:descriptor descriptor} | ||
[quo/approval-info | ||
(assoc state | ||
:button-label "Edit" |
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 preview becomes more powerful/useful if we parameterize as much as we can, so the person can check in the UI how the component behaves in more scenarios. tag-label
and button-label
could be in the state.
84% of end-end tests have passed
Not executed tests (1)Failed tests (4)Click to expandClass TestWalletMultipleDevice:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Expected to fail tests (4)Click to expandClass TestWalletOneDevice:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Passed tests (43)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityMultipleDevicePR:
Class TestWalletOneDevice:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestDeepLinksOneDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
|
@Francesca-G Could you please do a design review for this PR? |
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.
Here's the review with 2 minor details to fix, good job ✨
dfaa225
to
ce6b8c9
Compare
hi @ajayesivan, e2e failures are not PR related, thanks!
|
ce6b8c9
to
0c398e7
Compare
0c398e7
to
f2d6f83
Compare
Hi @ajayesivan ! I am wondering why this PR is not merged yet? |
fixes #20090
Summary
Implements the List Items/Avatar Info component
Testing notes
Manual QA can be skipped since this PR only adds a quo component and doesn't introduce any changes outside Quo Preview.
Platforms
Areas that maybe impacted
None
Steps to test
Quo Preview -> LIst Items -> Approval Info
status: ready