Repository navigation
refactor(coordinator): move browse cursor sync out of the hub - #3439
Merged
Merged
Conversation
datlechin
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Repo Hygiene is red on main. #3436 added
MainContentCoordinator+VisibleContainer.swift, taking the coordinator's extension files from 67 to 68, past the hub ratchet. The release tag needs main green.Change
BrowseCursorCoordinator, owned byMainContentCoordinatorlikeFindCoordinator. No behavior change..github/hub-ratchet-baseline.jsonrecords the four counts that went down since it was last written.Verified
check-hub-ratchet.pypasses.VisibleContainerFollowingTestsandWorkspaceAnchoringTestspass, updated only to reach the members through the new type.