-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix: correctly handle head propagation in content layer deferred rendering #12014
Conversation
🦋 Changeset detectedLatest commit: 0cb06d0 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
The code looks. Shouldn't this fix be sent to main
instead?
I guess there's nothing to prevent us fixing this in 4.x. I've been avoiding it in other stuff because it touches stuff that's changed, but this should be fine. I'll see if I can rebase it cleanly |
7f54d45
to
921a040
Compare
Let's see if this works... |
It's just a thought. Considering that we will be in beta for a few months, we should ponder if this fix is worth having in |
70b4b79
to
0cb06d0
Compare
Changes
Previously we were not correctly handling head propagation for MDX and Markdoc entries in content layer. This PR ensures the correct flag is included in the resolved Vite ID, and that these assets are correctly included when rendering.
Testing
The MDX head propagation test is updated to use content layer
Docs