[codex] Preserve route topology declaration order#47
Merged
ScriptedAlchemy merged 2 commits intoJun 22, 2026
Merged
Conversation
b95b6f9 to
a1444de
Compare
a1444de to
0f5a76e
Compare
Base automatically changed from
codex/harden-route-transforms-dev-lifecycle
to
perf/bundling-performance
June 22, 2026 23:19
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
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.
Summary
Context
This follows up on the Slack design note in /home/zack/Downloads/react_router_request.md. Most of that note describes a future in-place route topology design or items already covered by PR #46; this PR addresses the remaining small current-baseline correction that route order is semantic.
Verification