Question 1

How to add authentication to GraphQL endpoints with GraphQL Plug?

Accepted Answer

Since it uses Plug middleware, you can add authentication Plugs in the Phoenix pipeline before the GraphQL endpoint. For example, use `plug :authenticate_user` in the `:api` pipeline to secure requests.

Question 2

GraphQL Plug vs Absinthe: which is better for Elixir?

Accepted Answer

GraphQL Plug is minimal and ideal for simple integrations with Phoenix and GraphQL Elixir, while Absinthe offers a more feature-rich, mature ecosystem with subscriptions and better tooling. Choose GraphQL Plug for lightweight needs or Absinthe for production-ready complexity.

Question 3

Does GraphQL Plug support GraphQL subscriptions?

Accepted Answer

No, the README and features don't mention subscriptions. It focuses on basic HTTP-based queries and mutations, so you'd need to implement real-time features separately, possibly with Phoenix Channels.

Question 4

How to handle errors in GraphQL Plug responses?

Accepted Answer

Errors are managed through the GraphQL Elixir schema's resolve functions, which should return error tuples. The Plug handles JSON serialization, but custom error formatting requires schema-level adjustments.

Question 5

Can I use GraphQL Plug with an existing Phoenix REST API?

Accepted Answer

Yes, you can mount it alongside REST routes in Phoenix routers using scopes, allowing gradual migration or coexistence. The example shows using `forward` in a scope with the `:api` pipeline.

Question 6

What are the performance implications of using GraphQL Elixir?

Accepted Answer

Performance depends on the GraphQL Elixir implementation, which is less optimized than alternatives like Absinthe. For high-throughput APIs, benchmark carefully and consider the early-stage ecosystem's potential bottlenecks.

plug_graphql

What is plug_graphql?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions