fix: consistent headings format in api-reference.mdx#13316
fix: consistent headings format in api-reference.mdx#13316ArmandPhilippot merged 3 commits intov6from
api-reference.mdx#13316Conversation
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
left a comment
There was a problem hiding this comment.
This one looks great, too!
|
Thank you! Just noting that I wait to check the other references before merging this in order to make a single PR in core if other files also affect the configuration reference! (this shouldn't take weeks 😄 ) |
|
I'll check the links in the core repo and make a PR, so this one is ready to go! |
Same as #13315
For context: In a #13021 (comment), we decided we preferred
Type.prop(orobject.prop) as headings instead ofpropboth 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)
Uses a consistent heading format in
api-reference.mdx.Note that we'll need to update the config file in core to fix a link. I'll check the other references before to avoid doing this multiple times.
Related issues & labels (optional)