-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
treat tuples as lists #180
base: develop
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #180 +/- ##
========================================
Coverage 98.19% 98.19%
========================================
Files 14 14
Lines 1441 1441
========================================
Hits 1415 1415
Misses 26 26
Continue to review full report at Codecov.
|
Looks good to me, we just need to get tests added and then I'll merge this. I'm happy to write these if no one has time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, we just need to add a test for this and this is good to merge.
@@ -202,7 +202,7 @@ def visit_identity(self, node, value): | |||
def visit_index(self, node, value): | |||
# Even though we can index strings, we don't | |||
# want to support that. | |||
if not isinstance(value, list): | |||
if not isinstance(value, (list, tuple)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this is duplicated below I'd suggest moving this up to line 110 and add a LIST_TYPE
that we can reuse.
Hi. Are there any plans to have this merged soon ? |
I believe now any tuples in input data should be treated as lists.
use case described in the issue #179 now works as expected in the issue