-
Notifications
You must be signed in to change notification settings - Fork 987
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
Remove old quo code from status_im2 namespace #17404
Conversation
Testing lint in ci. I will request review once ready. |
Jenkins BuildsClick to see older builds (25)
|
5b3666d
to
823dac2
Compare
@@ -31,5 +30,4 @@ | |||
|
|||
(defn set-theme | |||
[value] | |||
(quo/set-theme value) |
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.
@Parveshdhull, it appears that this was introduced during the Refactor app theme management process. I am in the process of removing it as part of the refactoring. I wanted to inform you of this change and ensure that it does not impact any essential functionality.
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.
We need to put this quo/set-theme
usage back to fix the issue shared by @VolodLytvynenko here: #17404 (comment). Otherwise, the old UI elements will be broken until we fully migrate everything.
I can put this back and exclude this file from the linting script for now and create a follow-up issue to remove this usage later. @flexsurfer What do you suggest?
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.
let's do the hack for now, just set quo/set-theme to the atom and use atom here, so we could keep quo linting error, so nobody uses quo by mistake
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.
yeah i was wondering why you didn't remove quo.theme then, so it's still used
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.
@flexsurfer correct me if I'm wrong, but from my understanding, we can't start removing code until we remove all status_im usage from status_im2.
I didn't get what you meant by 'set quo/set-theme to the atom and use atom here'. Could you please elaborate?
823dac2
to
a4a3d62
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.
it seems like ns quo.theme
can be removed now
3f02515
to
f759236
Compare
42% of end-end tests have passed
Failed tests (25)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityOneDeviceMerged:
Passed tests (18)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
20% of end-end tests have passed
Failed tests (20)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Passed tests (5)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
60% of end-end tests have passed
Failed tests (17)Click to expandClass TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestCommunityMultipleDeviceMergedTwo:
Passed tests (26)Click to expandClass TestCommunityOneDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestActivityMultipleDevicePR:
Class TestCommunityMultipleDeviceMergedTwo:
|
From my understanding, the failing e2e tests are not related to this PR. Could someone from QA please confirm @status-im/mobile-qa? |
hi @ajayesivan currently, there are e2e failures occurring due to data delivery issues. I can quickly check manually to see if everything is alright. Could you please point out the possible areas that may be impacted by this PR? |
Hi @VolodLytvynenko, This PR removes the old quo usage in the new code and replaces it with the quo2 counterpart. I don't think this one requires any manual testing. I found 1 preexisting UI issue and reported it here: #17407. |
89% of end-end tests have passed
Failed tests (1)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Passed tests (8)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestActivityMultipleDevicePRTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
hi @ajayesivan one issue has been found that was introduced by this PR. The elements appear as light on the dark theme. This issue seems to affect only the old elements of the app, which I assume will be updated in the future. However, it looks a bit unattractive for now :) Is there something we can do to resolve this? Steps:
Actual result: |
e651489
to
4ef5b5e
Compare
@VolodLytvynenko I have fixed the issue you reported. Could you please test again? Thanks! |
72% of end-end tests have passed
Failed tests (12)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Passed tests (31)Click to expandClass TestActivityMultipleDevicePR:
Class TestActivityMultipleDevicePRTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
Hi @ajayesivan Thank you for fixed. Other issues are not related to this PR. Ready to be merged |
25% of end-end tests have passed
Failed tests (3)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Passed tests (1)Click to expandClass TestActivityMultipleDevicePRTwo:
|
@@ -1,5 +1,5 @@ | |||
(ns status-im2.common.qr-code-viewer.style | |||
(:require [quo.design-system.colors :as colors])) | |||
(:require [quo2.foundations.colors :as colors])) |
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.
🙏
4ef5b5e
to
5927967
Compare
fixes #17273
status: ready