-
-
Notifications
You must be signed in to change notification settings - Fork 684
Don’t set defaults for attrs
and content
in head entries
#3122
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
Conversation
🦋 Changeset detectedLatest commit: 844f0ba The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
✅ Deploy Preview for astro-starlight ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
size-limit report 📦
|
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.
Amazing, was planning to do this during lunch after noticing it while updating guides on my website for Starlight 0.33
but you already did it 🎉 🙌
Looks perfect to me, easier for users, easier for us in our tests, only wins all around.
I'll just have to update my guides again 😄
* main: [ci] release (withastro#3124) Fix E2E tests broken by formatter [ci] format Add built-in heading anchor link support (withastro#3033) i18n(fr): update `environmental-impact` (withastro#3123) Cascade Layers (withastro#2322) Fix image metadata validation in StarlightPage schema (withastro#3118) Don’t set defaults for `attrs` and `content` in head entries (withastro#3122) [ci] format i18n(es) Translate `route-data` (withastro#3071)
Description
attrs
andcontent
from the schema used to parse head entries (previously these were{}
and""
respectively).head
array without types saying you must set these default values.head
in some way, although for the average site this should be basically an internal API change.head
by linking toHeadConfig
, which shows these properties as optional.