-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add support for creating non-meta tags with v2_meta
#5746
Conversation
🦋 Changeset detectedLatest commit: 6dedab6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
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 |
...matches.map((match) => match.meta), | ||
]; | ||
export const meta = ({ data, matches }) => | ||
matches.flatMap((match) => match.meta); |
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.
While both technically work (React renders nested arrays of arrays just fine), the output of map
doesn't match our return type API.
🤖 Hello there, We just published version Thanks! |
This PR adds support for generating
<script type='application/ld+json' />
and meta-related<link />
tags to document head via the routemeta
function when using thev2_meta
future flag. This is useful for things like canonical URLs, alternate language references and structured data JSON.The added API looks like this: