This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
Replies: 1 comment
-
👍 I'd advocate for JMESPath instead (or additionally) but maybe that's because it is what I'm used to with the AWS cli. 😄 But I just stumbled across the need for this feature today. I got an absurdly long list of things back from an API I was calling and needed to reduce it down to just 2 properties for every item in that list. Unfortunately there was no graphql interface available for the data I wanted, and as a result ended up copying the data out of insomnium to go use a different tool. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
In my opinion, one of the best features of Insomnia, beside being completely local, was also its simplicity while being powerful.
When it comes to filtering JSON outputs from HTTP responses, most tools go with full testing bench, full JS scripts, post-request hooks, etc.
Insomnia, and Insomnium, have a simple field where you can type JSONPath and this is already very powerful and simple. It is one of the only serious HTTP GUI to offer this.
Allowing to also filter with
jq
would bring it to another league of its own, where you can actually select across multiple objects, and reshape JSON.Paw (now RapidAPI) does this beautifully with a dropdown to choose between JSONPath and jq. Honestly, if RapidAPI was not macos-specific, it would be the only tool I ever use again, just because of this.
I think Insomnium could really become the best in class by keeping the original spirit of Insomnia and bringing this feature.
There was some discussion about this in Insomnia, as well as some beginning of implementation it seems :
Beta Was this translation helpful? Give feedback.
All reactions