Improves truncate twig filter #12347
Merged
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
|
as it is security related (could introduce xss), before we could merge this we would need unit tests. |
|
actually it shouldn't be security related, as it doesn't change the string. But can add some test nevertheless. |
sgiehl
force-pushed
the
truncatefilter
branch
from
a04e712
to
5799ef3
Compare
|
Added some simple tests... |
mattab
modified the milestones:
3.5.0,
Priority Backlog (Help wanted),
Backlog (Help wanted)
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.
Currently the truncate twig filter might cut off encoded entities or cut strings to early if encoded entities are within it, this changes should prevent that.