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
When I type .results[], jnv correctly filters the results:
Then, if I additionally type some string, it seems jnv tries to evaluate the entire input text as a jq expression, completely reverting the filtering. This is extremely annoying because the input text being typed is of course generally an incomplete jq expression:
When I complete typing the expression, jnv again succeeds to evaluate the expression:
Question
Is it possible to disrespect (i.e. ignore) an incomplete jq expression being typed and instead fall back to the longest valid prefix?
I have this original JSON:
When I type
.results[]
,jnv
correctly filters the results:Then, if I additionally type some string, it seems
jnv
tries to evaluate the entire input text as a jq expression, completely reverting the filtering. This is extremely annoying because the input text being typed is of course generally an incomplete jq expression:When I complete typing the expression,
jnv
again succeeds to evaluate the expression:Question
Is it possible to disrespect (i.e. ignore) an incomplete jq expression being typed and instead fall back to the longest valid prefix?
For example:
.results[]
.results[]
.results[] |
.results[]
.results[] | select
.results[]
.results[] | select(.type ==
.results[]
.results[] | select(.type == "type1"
.results[]
.results[] | select(.type == "type1")
.results[] | select(.type == "type1")
Original JSON
The text was updated successfully, but these errors were encountered: