[Feature Request] For Graphql requests, show QUERY or MUTATION in the request tree

[rocketraman]

• Insomnia Version: 5.15.0
• Operating System: Fedora Linux

The request tree currently shows the HTTP verb for the request i.e. GET/POST/etc.

For GraphQL requests, this isn't that useful, since all are POSTs. What would be useful there, however, is to know whether the request is a query or a mutation. Can GraphQL requests be tagged this way as opposed to the verb?

[gschier]

I think that if Insomnia were a GraphQL-only IDE, this would be a no-brainer to add. However, I have a lot of hesitation to implement this.

Basically, Insomnia is a general purpose HTTP client. Part of being an HTTP client is showing HTTP things like URL, query params, authentication, verb, etc.

While implementing this is a small thing, I feel it would be the first step away from it's intended goal and requires starting a larger conversation where Insomnia should go in the future.

Some things to think about:

• How much of a protocol/spec/format should Insomnia natively support?
• Would more specific functionality be better suited as plugins? (like JetBrains IDEs do)
• Is GraphQL popular enough for there to be a completely separate app (Graphsomnia?)

Thanks for the message @rocketraman! Forgive me for unloading all of that on you 😄

[rocketraman]

@gschier I understand your concerns. When I wrote the request the inconsistency of it was bugging me, but I thought I'd throw it out there anyway. Glad its prompted this discussion.

I don't like the separate app approach. I use Insomnia for both GraphQL and regular REST calls and like the fact they are all in one place. Having to switch between two apps would be a pain. The GraphQL UX would have to be become significantly better to overcome that pain.

From a consistency perspective, I get you are showing the HTTP verb consistently. That is good. Perhaps support for an optional second tag which provides higher level protocol information would be useful, when such protocol-level information is available (such as with GraphQL queries vs mutations). Whether this second tag is populated by a plugin or by core features is an important decision that I can't add a lot to, but either way the user experience would be the same.

[4ekki]

Agree with rocketraman, I've started using Insomnia since it is either REST calls and GraphQL client in a single application and that is amazing.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rocketraman]

Still interested in this.

[gschier]

What happens if you have both a query and a mutation in a request?

[rocketraman]

What happens if you have both a query and a mutation in a request?

If you go the route of having secondary tagging for higher-level protocol information, then you could just show both?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.