-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Add ability to specify custom headers #148
Comments
Hi @asiandrummer yes, absolutely. I'll take a look into it. I already played with the example directory and got it working. What would be the best way to define custom |
I think you may have already looked at it, but refer to this example from the example code we have. It defines a custom The main reason why we'd prefer this is because we want |
@asiandrummer Thanks Hyo. I'm moving this here so we can have a way to place GraphiQL and custom versions of it as middleware. |
how i can use the middleware to input the headers ? I've tried plugins for chrome and app for mac, and none of them is working ? it's a pity no input headers in the original graphiql, looks dogmatic decision |
@webmobiles it's difficult to answer your question without knowing which middleware you're talking about and the plugins you've tried/without mentioning them. I heard that GraphiQL for Mac already supports a custom header, but have not seen it/used it myself. I think Lee's comment here, in addition to multiple responses we've given to explain this, best describes why we wouldn't support custom headers in GraphiQL. |
In many cases, we're using GraphiQL for debugging an API server in development. I think it's required that adding a field to the interface rather than change the behaviour programmatically.
|
@balthild You can checkout https://github.com/imolorhe/altair as well. |
@imolorhe Great project! |
…transform-es2015-duplicate-keys-6.24.1 Update babel-plugin-transform-es2015-duplicate-keys to the latest version 🚀
It would be great to have functionality to add custom headers for authorisation purposes within GraphQL.
The text was updated successfully, but these errors were encountered: