-
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
chore: remove uses of override theme prop #16570
Conversation
Jenkins BuildsClick to see older builds (28)
|
@@ -112,13 +112,11 @@ | |||
:component add-new-contact/new-contact} | |||
|
|||
{:name :how-to-pair | |||
:options {:theme :dark |
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 noticed these screens phone status bar (time/battery etc) was in the wrong color for the 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.
🚀
@@ -188,3 +188,5 @@ | |||
(if (= type :password) | |||
[password-input base-props] | |||
[base-input base-props]))) | |||
|
|||
(def input (quo.theme/with-theme input-internal)) |
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.
Yep @ibrkhalil pointed out you add docstring on the outer layer and it works. Perhaps someone can create a follow up issue to move the docstrings, and maybe even clean a few up while they're doing 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.
Even if we try that approach when we define the components in quo2.core
like this(def input quo2.components.inputs.input.view/input)
, the doc string is not being preserved.
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 docstring is metadata, it might be possible to forward it with functions like meta
, with-meta
, etc.
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.
@erikseppanen @J-Son89 @ajayesivan
Even if we add it as metadata, some IDEs/Editors (like IntelliJ) that perform static code analysis will not read the docstring.
87% of end-end tests have passed
Failed tests (5)Click to expandClass TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Passed tests (34)Click to expandClass TestActivityMultipleDevicePR:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
|
Hi @J-Son89 Could you please rebase the PR and resolve existing conflicts? After that we can perform manual testing. Thanx! |
@VolodLytvynenko - this is ready now 👍 |
88% of end-end tests have passed
Failed tests (5)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Passed tests (35)Click to expandClass TestActivityMultipleDevicePR:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
|
hi @J-Son89 thank you for PR. No issues from my side. Ready to be merged |
one further step towards: #16400
updates the usage of theme prop in
user_avatar
documentation_drawers
input
recovery phrase
preview list
filter selector
segmented tab
status tags
and removes the usage of
override-theme
for these components within the appTo Test:
This affects the theming of components so a quick walk through of the app and ensuring the theme is correct on components is correct should be enough here.