No need to encode '{}' because visual tokens are not used anymore #2625
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
escopecz
added
T1
|
?? |
escopecz
added
the
pending-test-confirmation
alanhartless
approved these changes
Oct 11, 2016
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.
Description:
In certain content the curly brackets in the tokens were encoded. The reason was from the time when Mautic used visual tokens.
Steps to test this PR:
{}will not be replaced.Steps to reproduce the bug:
{}were encoded after Save&Close or Apply+refresh.List deprecations along with the new alternative:
BuilderTokenHelper::replaceVisualPlaceholdersWithTokens()is deprecated