absinthe_plug
absinthe_plug copied to clipboard
absinthe-graphql
Plug support for Absinthe, the GraphQL toolkit for Elixir
I've been dancing around these unpredictable "is not a valid `Absinthe.Schema`" errors for months now, and finally took some time to figure out exactly what's going on. It turns out...
We recently discovered that supporting `multipart/form-data` POSTs in GraphQL servers makes it very likely that your server will be vulnerable to executing GraphQL mutations in CSRF attacks unless otherwise prevented....
Newer versions of Graphiql [support headers in the editor](https://github.com/graphql/graphiql/pull/1543), but it looks like the version of Graphiql in `absinthe_plug` doesn't have it.
I'm not quite sure if this should be part of the `Absinthe.Plug` API or if we should just dig into `Conn.private`. Do with it as you will!
If a developer wants to preserve context when executing a whole document, there needs to be an option to opt out of batched execution. https://github.com/absinthe-graphql/absinthe_plug/blob/master/lib/absinthe/plug.ex#L508 https://elixir-lang.slack.com/archives/C0PR49P4P/p1624455107364500
How can we disable multi-operation queries like "[{"operationName":"xxx1","variables":{},"query":"query xxx1 {*********}"}, {"operationName":"xxx2","variables":{},"query":"query xxx2 {*********}"}, {"operationName":"xxx3","variables":{},"query":"query xxx3 {*********}"},, ...repeat 1000x..." for security reason, we prefer to only allow a single operation per...
It seems that the latest version adds a lot of useful features.
Previously subscriptions over HTTP were handled through SSE. This commits adds a callback so the user can choose to handle it differently. It's modelled after how [graphl-ruby](https://graphql-ruby.org/subscriptions/pusher_implementation.html) does it. I...
So, this is the first step on a bigger journey to get the GraphiQL client(s) up to date. I might need little guidance here and there since I only started...
As per the spec (https://spec.graphql.org/October2021/#sec-Errors.Error-result-format) enables placing extra errors in the extensions field using `spec_compliant_errors: bool` plug option. In line with https://github.com/absinthe-graphql/absinthe/pull/1215, this is an optional prop with a default...
Metadata
Owner
Metadata
Plug support for Absinthe, the GraphQL toolkit for Elixir