fix: curly brace escaping in regular expression #570
Merged
Conversation
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
The modification in the code was to escape the curly braces ({})
by replacing them with \{ and \}.
This ensures that the curly braces are treated as literal characters
in the regular expression, addressing the issue caused
by their metacharacter usage.
sravan-s
approved these changes
May 30, 2023
HoonBaek
deleted the
fix/UIKIT-4027/curly-brace-escaping-in-regular-expression
branch
AhyoungRyu
pushed a commit
that referenced
this pull request
May 30, 2023
### Description Of Changes
The modification in the code was to escape the curly braces ({}) by replacing them with \{ and \}.
This ensures that the curly braces are treated as literal characters in the regular expression,
addressing the issue caused by their metacharacter usage.
[UIKIT-4027](https://sendbird.atlassian.net/browse/UIKIT-4027)
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 Of Changes
The modification in the code was to escape the curly braces ({}) by replacing them with { and }.
This ensures that the curly braces are treated as literal characters in the regular expression, addressing the issue caused by their metacharacter usage.
UIKIT-4027