-
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
chore: organise chats context #18373
Conversation
Jenkins BuildsClick to see older builds (12)
|
f576920
to
a4bad6d
Compare
(ns status-im.contexts.chat.new-chat.view | ||
(ns status-im.contexts.chat.home.new-chat.view |
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.
Is it only one file that needs to be under home
?
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.
Not sure exactly what you mean here?
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.
chat/home - any folder which may be used in the home page
I only see one file (and its style) under contexts.chat.home
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.
In this pr, under home there is
add_new_contact,
chat_list_item,
new_chat,
contact_request,
view (main entry point)
Happy to restructure it 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.
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.
Oh okay fine, these files weren't showing as changes cause they were already under a home namespace
a4bad6d
to
afe626d
Compare
@status-im/mobile-qa - this pr is just moving files and nothing is addde/removed here in the code. |
52% of end-end tests have passed
Failed tests (21)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePR:
Class TestActivityMultipleDevicePRTwo:
Expected to fail tests (2)Click to expandClass TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityOneDeviceMerged:
Passed tests (25)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestCommunityOneDeviceMerged:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestDeepLinksOneDevice:
|
@status-im/mobile-qa - can someone take a look at these test results and let me know if they are ok? :) |
@J-Son89 they are not ok 😂 |
haha, yeah I am never too sure of what margin to expect. Actually I see the unit/integration tests are failing. Let me check/fix that first! |
afe626d
to
b180c79
Compare
Okay, removing PR from the queue for now. Let me know when it's ready |
@qoqobolo - seems good now. I rebased. Also checked the tests locally and they passed, I think it was just something flaky there. |
@J-Son89 okay thanks, restarting e2e |
95% of end-end tests have passed
Expected to fail tests (1)Click to expandClass TestCommunityMultipleDeviceMergedTwo:
Passed tests (20)Click to expandClass TestActivityMultipleDevicePRTwo:
Class TestCommunityMultipleDeviceMerged:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityOneDeviceMerged:
Class TestActivityMultipleDevicePR:
|
@J-Son89 now they are okay :) |
b180c79
to
88c3a35
Compare
Thanks @qoqobolo! 🙏 |
Re organised the files within the Chat context.
The general idea is to have
chat/ <common-pieces> - any folder which may be used in both the home page and the messenger page
chat/home - any folder which may be used in the home page
chat/messenger - any folder which may be used in the messenger page
Notes:
Some further refactoring should be done to further separate the events for all of these. In general the Chat files are quite bunched in together and should be separated for maintainability. Often there is large files with multiple exports and it is hard to know what/where/how some files are being used.
Testing notes: Nothing is added or removed in this pr, I am just moving the location of files around.