Repository navigation
Extract python code blocks first, and then general code blocks - #20
Open
radinshayanfar wants to merge 2 commits into
Open
radinshayanfar wants to merge 2 commits into
radinshayanfar wants to merge 2 commits into
Conversation
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
1 participant
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.
This PR will modify the code_extract function of LCB. Instead of looking for triple backticks without language specification and picking the last code block, this PR will first look for python code blocks and use the last found one. If nothing is found, it then looks for code blocks without language specification pattern.
This fixes an issue where the model provides some more details, reasonings, or examples inside triple backticks after generating the soultion.