fix: handle frontmatter body
field in mdx
#451
Merged
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.
markdown documents can have a
body
markdown field in frontmatter, which will be processed correctly, e.g.:however, the same fails with mdx (contentlayer will use the top-level
body
field even fornested.body
):this is because the markdown field checks
isRootDocument
, but the mdx field does not. this pr makes the mdx field match the markdown field behavior.for context: i ran into this because netlify-cms will create these nested frontmatter
body
fields for "single file" collections with i18n.