Allow numerals in custom token class names #228
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.
Updates the snake regex used to convert custom token class names to render function names, to allow for the use of numerals.
Example use case is in writing custom functions for h1 - h6 elements. In this case, token class names are
CustomH1Token
toCustomH6Token
.Expected behavior is that it would attempt to invoke functions
render_custom_h1_token
torender_custom_h6_token
However, current behavior instead attempts to invoke the function
render_custom_h_token(self, token)
for all six classes.