Closed EnriqueSoria closed 2 years ago
Hey @EnriqueSoria 👋🏽
Thanks for having reported this weird behaviour. The culprit is the vendor https://github.com/savaki/jq this extension uses, as stated by https://github.com/savaki/jq/issues/7 and https://github.com/savaki/jq/issues/2.
I'm going to fix it ASAP.
Wow, that was a really quick fix! Thanks :heart:!
I would group this other enhancement https://github.com/valeriobelli/gh-milestone/issues/16 in the same release since both have breaking changes.
@EnriqueSoria, is this bug blocking you from going forward by any means?
I would group this other enhancement #16 in the same release since both have breaking changes.
@EnriqueSoria, is this bug blocking you from going forward by any means?
@valeriobelli For me it's not critical, I was just appreciating how fast you answered and fixed this. Thanks again for your interest!
I'll try to schedule a release by the end of this week, including the other enhancement I mentioned. If I fail to accomplish that enhancement, I'll release only the fix for this bug.
Description It appears that
jq
query is not parsed properly:when filtering with native
jq
it worksbut with
--jq
parameter it doesn'tCurrent behavior
Expected behavior
Environment: