allow toc_levels option to be of type Range - #210
Closed
jkraemer wants to merge 1 commit into
Closed
Conversation
Owner
|
Thanks, this is a good idea. However, the values of the array would need to be converted to integers in case the range isn't an integer range (see the array case). Please update your pull request in this regard. |
jkraemer
force-pushed
the
toc_levels_range
branch
from
January 21, 2015 07:00
ebcbb23 to
d3a8fbc
Compare
Contributor
Author
|
updated! |
Owner
|
Thank you - I have cherry-picked your commit! |
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.
This is more or less cosmetics but I just stumbled across this - the docs are talking of 'range syntax' but passing an actual
Rangefor the:toc_levelsoption didn't work.