api-rest

Is there an existing issue for this?

• I have searched the existing issues

Summary

It would be amazing to have an Authorization tab on GraphQL, as it is for REST.

Why should this be worked on?

Authorization is also a thing in GQL and having automated OAuth mechanism would be 👍

Support for closing with a reason was added in version 2.3 of the HTTP & WebSocket ASGI Message Format (2021-02-02).

Also decide whether we want a way to derive the reason from HTTPErrors like we do with the close code. Alternatives include just using the error's title, description, and adding a

Description

We have a vuejs frontend talking to a connexion-based REST API. We use jwt tokens. Sometimes, without any obvious trigger, we get the following exception:

File "venv/lib/python3.8/site-packages/flask/app.py", line 2464, in call return self.wsgi_app(environ, start_response)
File "venv/lib/python3.8/site-packages/flask/app.py", line 2450, in wsgi_app response = self.handle_

What would you like to be added:
A Fault injection filter should provide configurable error injection capabilities, such as delay, error local reply. it is best to have more detailed routing-based configuration capabilities

Why is this needed:
Because this is the ability that is required in the testing phas

Add a GitHub action flow for publishing a new version (run build, run tests, publish to npm and GitHub packates) etc.

https://github.com/sisense/graphql2rest/actions/new