Fix json parse bug #3
Open
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
Wzixiao
commented
May 18, 2024
| throw new Error("No valid JSON found in response content."); | ||
| } | ||
|
|
||
| const jsonString = rawContent.substring(startIndex, endIndex).trim(); |
There was a problem hiding this comment.
When there was no json_object a long time ago, my solution to this problem was to find the first "{" and the last "}" in the string, and then we parsed it
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
Solve the bug that the json data format returned by the gpt model is incorrect.
maybe with freeedcom#56 related