-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update LG escape #3614
Merged
Merged
update LG escape #3614
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
Can you add some test case around |
cosmicshuai
approved these changes
Mar 25, 2020
This was referenced Mar 25, 2020
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.
close: #3549
update LG escape policy to make LG achieve higher robustness.
the new strategy of LG evaluation about escape characters is as below:
\n
,\r
,\t
,\\
would be unescaped.\$
would be unescaped to$
\|
would be unescaped to|
\
prefix, would leave it as isExamples
Simple samples
Structure LG sample
would get:
json sample
would get the string result ->
Your meeting about "Adaptive Card design session"
fromFile sample
and the content of 1.txt is
would get the same string result ->
Your meeting about "Adaptive Card design session"