docs: fix nested list formatting in tgb docstring #2779#2880
Open
Rajat-Kumawat wants to merge 1 commit into
Open
docs: fix nested list formatting in tgb docstring #2779#2880Rajat-Kumawat wants to merge 1 commit into
Rajat-Kumawat wants to merge 1 commit into
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
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.
What type of PR is this? (Check all that apply)
Description
Fixed a formatting issue where the 3 levels of nesting inside the
on_actiondocstring for thesharedInputcomponent were not rendering correctly in IDEs like VS Code. Converted the raw HTML<ul>/<li>list structure to native Markdown formatting with proper indentation to guarantee clean nested bullet points.Related Tickets & Documents
How to reproduce the issue
Backporting
This change should be backported to:
Checklist
We encourage keeping the code coverage percentage at 80% or above.
If not, explain why:
If not, explain why:
If not, explain why:
If not, explain why: