-
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
[#18083] Implement Page top component #18163
Conversation
:auto-complete (when platform/ios? :none) | ||
:auto-complete (when platform/ios? :off) |
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.
Since the address-input
is being used by the page-top
component, I had to fix this, it throws a warning that breaks the tests
Jenkins BuildsClick to see older builds (5)
|
99235fd
to
8efa05a
Compare
:margin-horizontal 20}) | ||
|
||
(def recovery-phrase-container | ||
{:padding-vertical nil |
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.
What is :padding-vertical nil
for?
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's overriding the original recovery-phrase styles.
That component is setting padding-vertical
, in this PR we need the styles to be a different padding-top
and padding-bottom
, so just to make sure there isn't a padding vertical being passed.
(str "0" num) | ||
(str num)))) | ||
|
||
(defn- header-counter |
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.
What is the purpose of this counter?
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 |
it's not always we should treat figma components as quo components, imo, this one is the case, it doesn't look like a component, it's just a different combinations of different components that can be done in each view |
@OmarBasem And still not replacing the usages in this PR, as mentioned in the description, I'm planning to do it in a later one 👍 |
I agree. While creating it, I thought the same: it could be done on each screen. But when we create Currently, |
:community-name "Coinbase" | ||
:emoji "😝"}) | ||
|
||
(h/describe "Page 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.
Could you please also add the test rendering component without any 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.
Hi @vkjr
I'm wondering why do we want to sucessfully render the component without 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.
LGTM!
Hi @Francesca-G :) |
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 ✨
8efa05a
to
d7ce6a9
Compare
Merged without QA because it's a new component not used yet in screens |
fixes #18083
Summary
This PR implements the page top component:
https://www.figma.com/file/WQZcp6S0EnzxdTL4taoKDv/Design-System-for-Mobile?type=design&node-id=8737-151877&mode=dev
Review notes
There's a component called
text-combinations
(quo.components.text-combinations.view
) in the app, but it's not listed in figma and it has many usages across the onboarding and wallet screens, this new added component will substitute it since this is a full implementation of the figma designs (and the existing one is incomplete, for example, it doesn't contemplate inputs and context tags).I'm planning to refactor the wallet and onboarding screens using this component in a later issue.
Platforms
Steps to test
status: ready