Fix resolve() to handle direct list indexing#76
Merged
jph00 merged 2 commits intoAnswerDotAI:mainfrom Dec 30, 2025
Merged
Conversation
civvic
changed the title
civvic
changed the title
Contributor
|
Thanks! :) |
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
2 participants
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.
Fixes #75
The
resolve()function failed when given symbols likemylist[2](direct indexing without a dot). It worked forobj.attr[2]but notmylist[2].The regex split was treating
mylist[2]as a single part and trying to look it up as a key in globals. Added a check to handle direct indexing before the split.