fix: don't overwrite frontmatter description field where present
#2077
Conversation
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
barjin
changed the title
description field where presentdescription field where present
github-actions
bot
added
the
t-tooling
|
Preview for this PR was built for commit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Makes sure the custom
docusaurus.config.jsscript doesn't replace the customdescriptionfrom frontmatter, where it's present.Note
Avoid overwriting existing frontmatter descriptions by only generating a description when none is provided.
docusaurus.config.js):result.frontMatter.descriptionto only set an auto-generated summary when the frontmatterdescriptionis missing.Written by Cursor Bugbot for commit 04d5075. Configure here.