2
Active JSONPath filter not obvious
Source: Kong/insomnia#3549 · opened by @IanBurganMod
After filtering a response body with JSONPath, the filter remains on the response indefinitely. This is good, desired behavior, but when looking at a request that you may not have looked at for a while, the fact that it is filtered is not clear. For example, a developer might write $[0:3], not notice later, and be confused why there are only 3 items in the response. It is not immediately obvious that a JSONPath filter has been applied.
A possible solution would be to indicate that a filter has been applied by showing ... at the top of the response. Alternatively, it could be possible to indicate that a filter has been applied by highlighting the filter bar at the bottom with some color to show the filter is active. Really any indication that a filter has been applied other than the currently subtle change in font color at the bottom would be great.
A possible solution would be to indicate that a filter has been applied by showing ... at the top of the response. Alternatively, it could be possible to indicate that a filter has been applied by highlighting the filter bar at the bottom with some color to show the filter is active. Really any indication that a filter has been applied other than the currently subtle change in font color at the bottom would be great.
No pledges yet. Be the first to back this.
Comments
Similar requests
Use JMESPath instead of or in addition to JSONPath (JSONPath sucks.)
15 votes · 0 comments
JSONPath/XPath access to Environment Variables
1 vote · 0 comments
Turn on / off the JSONPath expression
4 votes · 0 comments
Enable variables in response filter and ability to use JQ as an option
1 vote · 0 comments
Indicate when response filter (JSONPath/XPath) input is invalid/non-existent
1 vote · 0 comments
No comments yet.