Support for Rendering Custom JSON Sections Starting with "```" #20325
Conversation
This file contains 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
salihozkara
changed the title
` 
EngincanV
approved these changes
Jul 30, 2024
gizemmutukurt
requested review from
oykuermann and
gizemmutukurt
and removed request for
gizemmutukurt and
oykuermann
gizemmutukurt
approved these changes
Aug 2, 2024
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.
Description
This PR addresses the issue where custom sections (e.g., docs-params section) that start and end with
````were being detected and rendered correctly, but sections starting with```were not being recognized and were rendered as normal markdown. With this PR, custom JSON sections that start with```will also be rendered correctly.This change aims to improve user experience by allowing for more flexible definition and rendering of custom JSON sections.
Checklist