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.
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
Site Editor: Prepare route registration by refactoring the site editor router #66030
Site Editor: Prepare route registration by refactoring the site editor router #66030
Changes from all commits
f52be94
da9f6d0
3ae6f53
99982c0
1509763
29bfd10
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 had forgotten why this didn't have a
mobile
area until I reviewed thelayout
component. Prepared #66309 to document when each area is present. It also prevents theedit
area from being rendered if the canvas mode is edit.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.
Does the
canvas
mode really warrant a separate route? Aside from themobile
view it still renders the same sidebar and the same<Editor />
component. Thecanvas
mode is managed by thecanvasMode
state in the data store and synced by theuseSyncCanvasModeWithURL
.In my view the canvas mode should be eventually managed only at one place; either:
a) in the route handler, which passes the mode down as
<Editor canvasMode={ params.canvas } />
prop;b) inside the
<Editor />
component which reads the mode from the URL itself. This setup is very similar to how you would work with "minor" query params likeorder=asc
orsearch=foo
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.
No disagreement, the main reason for the route is "mobile". I don't know how to handle it otherwise. For mobile, these routes render different things depending on the canvasMode. Not entirely sure how to handle it.
Aside: I would love to remove that duplicate state as well and only rely on the url but that is a separate large effort IMO.
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 agree this is worth revisiting, although I should point out that I like the rigidity of the current proposal: other than the
match
predicate, everything else is static data, making the whole thing IMO very easy to keep track of. It's more difficult for surprising behaviour to creep in, especially once we start considering third-party use. (Note that this remark doesn't imply that addressing themobile
view in a smarter way would necessarily go against the principle.)