Allow parsing needs options as multiline rst in custom layout #1397
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
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.
Hello,
When using the
meta()function in the custom layouts, it's not possible to parse the needs options as rst, only the links are handled in a custom way and the rest is parsed only with inline rst syntax.I have the need to be able to put multiline rst for some custom options and thought a dedicated
meta_rst()function would be the best way to handle those.I made this in an hour to see the feasibility of such a function so don't hesitate to tell me if there is anything that needs to be changed or improved. I also didn't touch the tests, I would need a bit a guidance to add/update tests for this feature.
Status: