Bugfix/31 anchor name formatting amends #34
Merged
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.
Description
Example:
was producing an anchor of:
we-039-d-love-to-hear-from-you
, while{% apply anchors() %}
and|anchors
were producing:wed-love-to-hear-from-you
.Now all 3 options produce:
wed-love-to-hear-from-you
.lowercase
attribute, which defaults tofalse
and produces the same behaviour as before. If set totrue
, it ensures that the entire anchor is lowercase.The default behaviour stays as is: lowercase words that are all uppercase and lowercase the first letter in any other case.
Example:
still produces:
pitch-fAQs
produces:
pitch-faqs
Applies to v2 and v3.
@brandonkelly if you think point 2 is not something we should pursue or it should be changed to a configuration setting, please let me know, and I’ll adjust. I’m thinking this version gives the best flexibility.
Related issues
#31