You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Single-Level vs Multi-Level Wildcard produces unexpected result on Predicate #70
Dear @JohnBehnke, thanks for reporting this. Using the main branch, both expressions fail for me and return null. Can you please double check that on your end and also report the version you're using? Thanks!
@aeberhart Thank you for looking! I'm using 0.9.8. I tried the main branch and double checked in my project (using 0.9.8), and I get null for result and the first object for result2
Activity
Single-Level vs Multi-Level Wildcard produces unexpected result on
aeberhart commentedon Sep 27, 2025
Dear @JohnBehnke, thanks for reporting this. Using the main branch, both expressions fail for me and return null. Can you please double check that on your end and also report the version you're using? Thanks!
JohnBehnke commentedon Sep 28, 2025
@aeberhart Thank you for looking! I'm using
0.9.8. I tried the main branch and double checked in my project (using 0.9.8), and I getnullforresultand the first object forresult2aeberhart commentedon Sep 29, 2025
Thanks! We'll look into this ASAP. I guess you're using ** as the workaround?
JohnBehnke commentedon Sep 29, 2025
Thank you for looking into this! Yeah, the
**works in my use case since its a flat array.fix test and add new wildcard test (* on array of object) #70