[Feature Request] GPQL identifier for GraphQL requests
See original GitHub issue- Insomnia Version: 7.0.3
- Operating System: Arch Linux 5.3.10
Details
Would be possible to add an identifier “GPQL” (or something like that) for GraphQL requests? For example, I have to set the following description in order to identify my GraphQL requests:
The POST
identifier here isn’t helping so much. If the identifier became GPQL, I would be able to name those requests like this:
I understand those identifiers are for HTTP methods, but GraphQL could be an exception.
Best regards, Rafael Pacheco.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Global Object Identification - GraphQL
For this to work, a client will need to query via a standard mechanism to request an object by ID. Then, in the...
Read more >The Anatomy of a GraphQL Request – The Guild
Clients send HTTP requests to the server with a payload that contains an operation document string (query, mutation, or subscription), ...
Read more >Metrics and logging - Apollo GraphQL Docs
Studio aggregates and displays information for your schema, queries, requests, and errors. You can also configure alerts that support Slack and Datadog ...
Read more >Requests and Responses - GraphQL - Dgraph
In this section, we'll cover the structure for GraphQL requests and responses, how to enable compression for them, and configuration options ...
Read more >spring boot query param
The @RequestParam annotation binds the web request parameter to a controller ... Custom queries with Spring Data JPA @Query lets you define JPQL...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Another option, an way more flexible, is a feature to add a badge (like that small graphql on the print above) with any text at all.
For example, for those 2 specific requests I would right click on them, select the “Add badge” option and type “graphql” on it. Even further, the dialog could have a combobox with predefined values (request types) and a field to type any custom value, up to a predefined string length.
What do you think?
That will solve the issue of identifying POST requests that are GraphQL, thanks 😄