Skip to content

[pull] canary from vercel:canary #256

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

Merged
merged 4 commits into from
Aug 6, 2025
Merged

[pull] canary from vercel:canary #256

merged 4 commits into from
Aug 6, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Aug 6, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

mischnic and others added 4 commits August 5, 2025 23:55
…nts (#82383)

When constructing the loader tree for parallel route segments, we inject
a `children` segment, which could contain things like slot level
layout/error/loading files. We want a way to distinguish between these
virtual segments that exist just for organizational purposes rather than
relying on `children`. This updates the loader tree construction code to
give these more unique names. In the future, we should see if we can
remove the need for this virtual segment if there are no special files
needed at that segment of the tree.
@pull pull bot locked and limited conversation to collaborators Aug 6, 2025
@pull pull bot added the ⤵️ pull label Aug 6, 2025
@pull pull bot merged commit fc70d77 into code:canary Aug 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants