Conversation
tridev-tej
reviewed
Feb 13, 2026
tridev-tej
approved these changes
Feb 13, 2026
02cff3d to
fd8e914
Compare
princesaroj111
approved these changes
Feb 13, 2026
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
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.
Currently, if LLM outputs
"C:\\my\\path"(which is correct JSON encoding ofC:\my\path), taskgen returns"C:\\\\my\\\\path"(i.e.C:\\my\\path). Also, if LLM outputs"C:\\test\\path", taskgen returns"C:\\\test\\\\path"(not"C:\\\\test\\\\path").This was caused by parsing strings from JSON using
match[1:-1]followed byremove_unicode_escapeinstead of justjson.loads(match).Script to reproduce:
Before PR:
taskgen output: {'Key': '\\\\a\\\n\\\t\\\\b'}After PR:
taskgen output: {'Key': '\\a\\n\\t\\b'}