-
Notifications
You must be signed in to change notification settings - Fork 137
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
Fixed indexed-repeat argument path evaluation in integer column type #499
Fixed indexed-repeat argument path evaluation in integer column type #499
Conversation
Codecov Report
@@ Coverage Diff @@
## master #499 +/- ##
==========================================
- Coverage 83.86% 83.85% -0.01%
==========================================
Files 25 25
Lines 3693 3691 -2
Branches 860 859 -1
==========================================
- Hits 3097 3095 -2
Misses 452 452
Partials 144 144
Continue to review full report at Codecov.
|
This doesn't look right. It will keep failing for every type other than text or integer which is not what we want. I think the difference in behavior is between calculates and non-calculates so perhaps that condition should be |
@lognaturel Thanks! |
Paul told me a couple of indexed-repeat expressions that could cause an issue, like indexed-repeat inside an if-else, or indexed-repeat as an expression, or indexed-repeat as an argument in other function like concat(), substr(). I think those cases are already tested, right? In the previous commit I've already removed the branching statement, please review it. Thanks! |
Still waiting for your review/resolve. Thanks! |
Happy New Year and I'll try to take a look by the end of the week. Please see #507 for a new test to add. |
Thanks @lognaturel and @gushil! |
Closes #484
Closes #507
Why is this the best possible solution? Were any other approaches considered?
Previous solution (PR #485) with added evaluation for integer type column.
What are the regression risks?
None.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
No.
Before submitting this PR, please make sure you have:
tests_v1
nosetests
and verified all tests passblack pyxform
to format code