Support for AsciiDoc fenced code blocks #938
Open
+92
−18
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
|
More general, it would also be nice to let the user enable this for any language (e.g. using a custom delimiter), or classes of languages (plain text styles, markdown dialects etc.). |
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.
First of all, thanks for the great extension. My team and I have been using it extensively in the last couple of months, and we consider this to be an essential part of our workflow. One useful addition would be to allow requests to be sent from
asciidoc-files. This would enable tighter integration of writing documentation in our workflow.I've created this PR for exactly this reason and based it on the very similar PR #933.
Happy to have your feedback on this!