support for passing headers about graphiql-rails HOT 5 CLOSED

It's probably out-of-scope. I mean, you're talking about accepting user input then sending that along with requests, right? So it would need a UI and glue code? My impression is that time would be better spent wrapping graphql-workspace, since it has so many other good features!

from graphiql-rails.

After playing with this for just a few minutes, the react project above has a lot of niceties that this project could benefit from.

How would you feel about wrapping that library?

from graphiql-rails.

Hi, I think it's be a great idea to have a Ruby-ready wrapper of that project! I think it would be possible to make an event better library, too, making a Rack app instead of a Rails engine, so that even non-Rails (and non-Sprockets) apps could use it. Let me know how it goes!

from graphiql-rails.

@rmosolgo Do you think header-passing is out of scope for this library? Or are you too busy to propose this as a feature?

Or do you prefer no issues and PRs only?

from graphiql-rails.

Correct--with this library, there's no way to pass a JWT/Bearer token as a header.

It's really sad about OSS...so little time and so much that the community needs.

from graphiql-rails.