doc: Fix native reStructuredText example for tags, surrounding them with brackets #225
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
posativ
added a commit
that referenced
this pull request
Nov 23, 2014
doc: Fix native reStructuredText example for tags, surrounding them with brackets
|
Thanks |
|
Super! |
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.
Here is yet another small fix in doc, unifomizing how tags must be set in reStructuredText example entry with others (YAML, markdown).
As a side note, it could be cleaner IMHO if in native metadata style (markdown, reST) those brackets could be ignored. I tried but failed to quicly find where parsing tags occurs, to measure feasability of such a change. What do you think about ?-)