Open
Conversation
You can now specify the start and end of code blocks via string labels. This greatly improves the experience because you can edit the source file and rely on the string labels to grab the correct code blocks. No more adjusting line numbers after making edits
f8a9bfe to
33d6844
Compare
33d6844 to
4d951ec
Compare
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.
Added support for string-based attributes. Also added 2 new range attributes:
start-afterandend-before.This addition is based on the Sphinx literal-include directive: https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#directive-literalinclude
It allows you to specify the code-block range using code comments instead of line numbers. This allows for editing of the included code file without having to re-figure-out the numeric ranges you want to include.