📃 Fix example to work better with deno doc and lsp #875
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
taras
approved these changes
Jan 2, 2024
The examples in the docs were not rendering properly on the deno doc site, and also inside the LSP for a number of reasons. This normalizes how examples are identified: - use fully qualified language name. I.e. "javascript" instead of "js" - remove any captions
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.
Motivation
The examples in the docs were not rendering properly on the deno doc site, and also inside the LSP for a number of reasons.
Borked language highlighting:
Captions don't seem to work
Approach
This normalizes how examples are identified: