Clarify title filter behavior in Templating docs#1481
Open
davidjb wants to merge 1 commit into
Open
Conversation
The example below this change shows the correct behavior - `| title` will title case each word in a string, not just the first character.
|
I've made another proposal (#1521) - sorry, I haven't seen yours. That one also specifies that the remaining letters will be turned lowercase. |
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.
Summary
Proposed change:
This PR updates the Templating docs to correct the explanation of the behavior of
title. Previously, the docs indicate that only the first character in a string will be upper-cased but the example (and behavior as I've just tested) is thattitlewill upper-case each word in a string, not just the first character. For avoidance of doubt, https://jinja.palletsprojects.com/en/stable/templates/#jinja-filters.title clearly sets out the intended behavior.Checklist
I've completed the checklist below to ensure I didn't forget anything. This makes reviewing this PR as easy as possible for the maintainers. And it gets this change released as soon as possible.