-
Notifications
You must be signed in to change notification settings - Fork 34
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
Inconsistent behaviour with asterisk-wildcard in array path #601
Comments
There's a pattern w.r.t. how they're implemented internally:
|
You mean it should work without
and
|
Oh, I guess you meant
So this is the expected output for "TEST_THREE" : [ {
"1" : "One",
"2" : "Two",
"3" : "Three"
} ] |
No actually this is an error in my fix. I corrected it TEST_3 is connected to the reverse handling that is commented out: |
Okay. But |
fixed (why are my code snippets not working?) |
Which code snippets? |
Turned all examples into unit tests. |
Will revisit after metafacture/metafacture-fix#102. |
and for the functions that are discussed in #121
and for the functions that are discussed in #121
@blackwinter should we split this issue in single tickets? |
No. Only if/when it turns out that the root causes are actually different and not fixable in one go. |
Since we do not have a ticket for that here. The asterisk wildcard in array paths seems to work sometimes, sometimes not and sometimes it breaks. I have set up a test with multiple usages of the
*
-wildcard and separated between working, breaking and no-doers. I am not sure if this is due to inconsistent array handling or due to the function. But I think it is good to collect them here:https://github.com/TobiasNx/fix-FunctionalReview-Testing/blob/a8f314ce0c416073873553166eb9116e41a95cb7/data/testing/asteriskArray
Following functions work, also with arrays in arrays:
prepend
append
replace_all
copy_field
works with single asterisk but not with arrays in arrays.Following do nothing:
split_field
sort_field
add_field
Following break with asterisk:
reverse
sum
rename
The text was updated successfully, but these errors were encountered: