Skip to content
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

Merged
merged 5 commits into from
Dec 20, 2023
Merged

Conversation

ulisesmac
Copy link
Contributor

@ulisesmac ulisesmac commented Dec 13, 2023

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

image image

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

  • Android
  • iOS

Steps to test

  • Open Status
  • Navigate to quo 2 library -> text combinations -> page-top

status: ready

Comment on lines -118 to +119
:auto-complete (when platform/ios? :none)
:auto-complete (when platform/ios? :off)
Copy link
Contributor Author

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

@status-im-auto
Copy link
Member

status-im-auto commented Dec 13, 2023

Jenkins Builds

Click to see older builds (5)
Commit #️⃣ Finished (UTC) Duration Platform Result
99235fd #1 2023-12-13 02:30:56 ~5 min tests 📄log
✔️ 99235fd #1 2023-12-13 02:34:05 ~8 min android-e2e 🤖apk 📲
✔️ 99235fd #1 2023-12-13 02:34:14 ~9 min android 🤖apk 📲
✔️ 99235fd #1 2023-12-13 02:38:20 ~13 min ios 📱ipa 📲
✔️ 99235fd #2 2023-12-13 02:42:23 ~2 min tests 📄log
Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ 8efa05a #3 2023-12-13 02:50:08 ~4 min tests 📄log
✔️ 8efa05a #2 2023-12-13 02:52:15 ~6 min android 🤖apk 📲
✔️ 8efa05a #2 2023-12-13 02:53:08 ~7 min android-e2e 🤖apk 📲
✔️ 8efa05a #2 2023-12-13 02:58:52 ~13 min ios 📱ipa 📲
✔️ d7ce6a9 #4 2023-12-20 19:13:37 ~4 min tests 📄log
✔️ d7ce6a9 #3 2023-12-20 19:14:39 ~5 min ios 📱ipa 📲
✔️ d7ce6a9 #3 2023-12-20 19:15:36 ~6 min android-e2e 🤖apk 📲
✔️ d7ce6a9 #3 2023-12-20 19:16:52 ~7 min android 🤖apk 📲

@ulisesmac ulisesmac force-pushed the 18083-page-top-component branch from 99235fd to 8efa05a Compare December 13, 2023 02:45
:margin-horizontal 20})

(def recovery-phrase-container
{:padding-vertical nil
Copy link
Contributor

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?

Copy link
Contributor Author

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
Copy link
Contributor

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Match the component styles:

image

that 00/00

@OmarBasem
Copy link
Contributor

The text-combinations is used in many places. Have you checked that everything looks fine?

@flexsurfer
Copy link
Member

flexsurfer commented Dec 13, 2023

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

@ulisesmac
Copy link
Contributor Author

The text-combinations is used in many places. Have you checked that everything looks fine?

@OmarBasem
I'll ask for a design review in this PR.

And still not replacing the usages in this PR, as mentioned in the description, I'm planning to do it in a later one 👍

@ulisesmac
Copy link
Contributor Author

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

@flexsurfer

I agree. While creating it, I thought the same: it could be done on each screen.

But when we create page-top as a component and use it, we make sure margin, paddings, sizes, etc, are correct. IMO, that is easier than replicating the same composition of components on each page.

Currently, text-combinations is the one used in many screens (onboarding and wallet namespaces), and page-top is just the complete implementation of if.

:community-name "Coinbase"
:emoji "😝"})

(h/describe "Page Top"
Copy link
Contributor

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?

Copy link
Contributor Author

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?

Copy link
Contributor

@mmilad75 mmilad75 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ulisesmac
Copy link
Contributor Author

Hi @Francesca-G :)
I'll need a design review for this component

Copy link

@Francesca-G Francesca-G left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work ✨

@ulisesmac ulisesmac force-pushed the 18083-page-top-component branch from 8efa05a to d7ce6a9 Compare December 20, 2023 19:08
@ulisesmac ulisesmac merged commit 7cf3165 into develop Dec 20, 2023
6 checks passed
@ulisesmac ulisesmac deleted the 18083-page-top-component branch December 20, 2023 19:17
@ulisesmac
Copy link
Contributor Author

Merged without QA because it's a new component not used yet in screens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Archived in project
Development

Successfully merging this pull request may close these issues.

Implement page top component
7 participants