-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
core[patch]: Fix "Bad control character in string literal" #5160
Merged
jacoblee93
merged 4 commits into
langchain-ai:main
from
Huaichen:Huaichen-patch-PR#5135
Apr 22, 2024
Merged
core[patch]: Fix "Bad control character in string literal" #5160
jacoblee93
merged 4 commits into
langchain-ai:main
from
Huaichen:Huaichen-patch-PR#5135
Apr 22, 2024
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
The error "Bad control character in string literal" occurs when calling JSON.parse(json). This typically happens because the JSON string contains control characters that are not allowed, such as newline characters. Any control characters in the JSON string should be escaped before parsing it using JSON.parse().
Added a test for PR# langchain-ai#5135. Added a few newlines to the JSON text, which will result in an "Bad control character in string literal" error before the fix.
dosubot
bot
added
the
size:M
This PR changes 30-99 lines, ignoring generated files.
label
Apr 20, 2024
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
bot
added
the
auto:bug
Related to a bug, vulnerability, unexpected error with an existing feature
label
Apr 20, 2024
jacoblee93
changed the title
Fix "Bad control character in string literal"
core[patch]: Fix "Bad control character in string literal"
Apr 22, 2024
…Huaichen-patch-PR#5135
jacoblee93
reviewed
Apr 22, 2024
Thank you! One small question |
jacoblee93
added
question
Further information is requested
lgtm
PRs that are ready to be merged as-is
labels
Apr 22, 2024
Thank you! |
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.
The error "Bad control character in string literal" occurs when calling JSON.parse(json). This typically happens because the JSON string contains control characters that are not allowed, such as newline characters. Any control characters in the JSON string should be escaped before parsing it using JSON.parse().
A test is added to "langchain-core/src/output_parsers/structured.ts" with adding several newlines into the json. The test failed due to "Error: SyntaxError: Bad control character in string literal in JSON at position 36 (line 2 column 36)".
The code in parse() was updated by replacing the newline literal inside a string element with '\n', and removing the newline literal outside of the string elements.