fix: consistent headings format in content-loader-reference.mdx#13317
Merged
ArmandPhilippot merged 4 commits intov6from Feb 27, 2026
Merged
fix: consistent headings format in content-loader-reference.mdx#13317ArmandPhilippot merged 4 commits intov6from
content-loader-reference.mdx#13317ArmandPhilippot merged 4 commits intov6from
Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
sarah11918
reviewed
Feb 27, 2026
Member
sarah11918
left a comment
There was a problem hiding this comment.
Agreed! I love being able to get rid of #cachehint-2 😂 Great improvement!
Member
Author
|
Thanks! I take this as an explicit approval... If not, please scream while I update the branch. 😄 |
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.
Same as #13315 and #13316
For context: In #13021 (comment), we decided we preferred
parent.childas headings instead ofchildboth for readability and linking. We already use this format in some modules reference (e.g. envField) but most of the modules were using the old format (e.g. action).Description (required)
Updates
content-loader-reference.mdxto use a consistent heading format (parent.child).I also removed two headings (
Loader propertiesandLive loader properties) because we usually don't use those... and I feel this is no longer necessary with theparent.childnotation. (btw we had a nesting issue for one of them)This one implies a lot of links updates... but I personally think this is nice (e.g.
#entries-1vs#livedatacollectionentries).Related issues & labels (optional)