-
Notifications
You must be signed in to change notification settings - Fork 86
chore: don't enforce the HomePage as the start section #18672
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: don't enforce the HomePage as the start section #18672
Conversation
@@ -701,6 +701,8 @@ method load*[T]( | |||
enabled = true, | |||
) | |||
self.view.model().addItem(homePageSectionItem) | |||
if activeSectionId == homePageSectionItem.id: |
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.
Remembering the HomePage as any other section
@@ -863,8 +865,9 @@ method load*[T]( | |||
self.marketModule.load() | |||
|
|||
# If the home page is enabled, we default to it as the opening section | |||
if homePageEnabled: | |||
activeSection = homePageSectionItem | |||
# (disabled for 2.35 as per https://github.com/status-im/status-desktop/issues/18664, revisit after) |
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.
Disabled the part where we enforced the HomePage
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 thought we can just set homePageEnabled=false
, no? 🤔
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.
Hmm no, we're not disabling the HomePage here, we're just restoring the old behavior where the last used section is remembered on the next app start
Jenkins BuildsClick to see older builds (40)
|
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.
Thank you!
This should be based on release branch, shouldn't it?
@@ -863,8 +865,9 @@ method load*[T]( | |||
self.marketModule.load() | |||
|
|||
# If the home page is enabled, we default to it as the opening section | |||
if homePageEnabled: | |||
activeSection = homePageSectionItem | |||
# (disabled for 2.35 as per https://github.com/status-im/status-desktop/issues/18664, revisit after) |
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 thought we can just set homePageEnabled=false
, no? 🤔
It will, once the e2e is fixed |
a379ab0
to
8682bc8
Compare
@anastasiyaig once e2e tests are fine, you can let me know. I'm taking over this PR while Lukas is off |
alright sure @jrainville its almost done, should be ready tomorrow |
8682bc8
to
7963d06
Compare
- treat the HomePage as any other section Fixes #18664
7963d06
to
baa5dec
Compare
baa5dec
to
5dd76b1
Compare
@jrainville i am done with my changes in this PR |
What does the PR do
Fixes #18664
Affected areas
AppMain
Architecture compliance
My PR is consistent with this document: QML Architecture Guidelines
Screencapture of the functionality
Zaznam.obrazovky.z.2025-08-20.17-39-19.mp4
Impact on end user
No more special treatment of the HomePage, last active section will always be the one we start with the next time
How to test
Risk