Uh oh!
There was an error while loading. Please reload this page.
feat(use-content-head): add helper for <head> binding - #1295
Merged
Conversation
…Doc and documentDriven
✅ Deploy Preview for nuxt-content ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
atinux
self-requested a review
June 27, 2022 13:48
atinux
commented
Jun 27, 2022
Member
Can you fix the lint error? |
atinux
reviewed
Jun 27, 2022
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
❓ Type of change
📚 Description
This PR adds
useContentHead(document: ParsedContent, to: RouteLocationNormalized = useRoute())function.It gives easy access to
<head>binding in both<ContentDoc>anddocumentDrivenfeatures.It is easily toggleable for
<ContentDoc />via the newheadprops.If you want to remove the binding from
documentDriven, you can overwrite the default[...slug].vuepage.Documentation has been updated.
Also fixes the latest issues with documentDriven
patherrors. 😬📝 Checklist