Bugfix/Escape JSON in Prompt Message #3901
Merged
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
JJK801
pushed a commit
to JJK801/Flowise
that referenced
this pull request
Feb 3, 2025
add fix to only get variables when there is no colon
This was referenced Mar 7, 2025
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.
Bug: Currently when you are trying to ask LLM to output a JSON by giving a few examples in the prompt, langchain/flowise by default will get everything enclosed in curly brackets as variables. Therefore, it will incorrectly identify the JSON examples as variables.
#968
Fix: Identify if there is a colon
:within the curly brackets, if yes, we will not extract the value as variable.