-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sidebar: Global Navigation #23602
Merged
Merged
Sidebar: Global Navigation #23602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generated by 🚫 Danger |
kean
force-pushed
the
task/sidebar-global-navigation
branch
from
September 16, 2024 12:27
b301788
to
337667d
Compare
📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
|
kean
force-pushed
the
task/sidebar-global-navigation
branch
from
September 16, 2024 15:00
dfe07d9
to
df6b060
Compare
kean
force-pushed
the
task/sidebar-global-navigation
branch
from
September 16, 2024 19:26
f88bae1
to
f44b164
Compare
crazytonyli
approved these changes
Sep 16, 2024
@@ -114,7 +114,7 @@ private func showSuccessNotice() { | |||
|
|||
private final class DebugMenuViewModel: ObservableObject { | |||
var blog: Blog? { | |||
RootViewCoordinator.sharedPresenter.mySitesCoordinator.currentBlog | |||
RootViewCoordinator.sharedPresenter.currentlyVisibleBlog() | |||
} |
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.
This blog
is not used and can be deleted.
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.
Done. It used to be needed for Quick Start, but now it's gone.
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements the remaining
RootViewPresenter
methods. It required a lot of small changes, so I split them into individual commits to make them easier to review but kept them in the same PR.Changes:
currentViewController
which was used only for blogging prompts. I recorded the test.MeScenePresenter
and replaces it with a newshowMeScreen
method. It was used for the Spotlight search which I tested here.currentlySelectedScreen
is used for analytics. I used the same names as the tab bar for now.readerNavigationController
fromReaderCoordinator
to make it stateless – it now simply calls the root presenter. The code topopViewController
never worked because by the time it is reached, the coordinator is deallocated. Not sure why it was added there in the first place – simply showing a "post failed" message seems ok (video).readerTabViewController
and replaces it with a standardswitchToDiscover
method. I recently made some changes in that area and tested it. It does work exactly as before (video).ReaderCoordinator
into a struct and removing it fromRootViewPresenter
– it's now just a bag of functions.mySitesCoordinator
. It adds sharedshowJetpackOverlayForDisabledEntryPoint
implementation that's just shown on top of the current root (video). It works on iPad too.showBlogDetails(for:then:userInfo:)
method. It's easy to test with universal links. These paths now work in any context: iPhone, iPad, iPad Split View.showManagePlugins
. The new flow users the exiting approach withuserInfo
(should prob be a new sections, but that's OK for now). It makes no sense for deep links to re-play the manual user navigation in the flow, so it opens "Manage" directly: iPhone, iPad. On iPad, site menu is not selected, but I'm not fixing it now.showStats(...)
fromMySitesCoordinator
toRootViewPresenter
and implements it using the existingshowBlogDetails(for:subsection:)
API. In action: iPhone, iPad.showCreateSheet
as a response for the blogging reminder notification. It was doing too much. The users know how to start a new post, so the app will simply open the blog from the notification for them.sharedPresenter.mySitesCoordinator.currentBlog
calls. Known issue: not working correctly for the Split View mode, but I'll address it separately.mySitesCoordinator
fromRootViewPresenter
🥵To test:
Follow the steps from the recordings added next to the changes.
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: