Question 1

How to set up GraphQL in Phoenix with graphql-elixir?

Accepted Answer

Use the plug_graphql dependency to handle HTTP requests in Phoenix. Refer to the hello_graphql_phoenix repository for example code and integration steps.

Question 2

GraphQL Elixir vs Absinthe: which is better?

Accepted Answer

GraphQL Elixir is a minimal, transport-agnostic core ideal for custom implementations, while Absinthe is a full-featured framework with more conveniences like built-in HTTP support and a larger ecosystem. Choose based on control vs. speed of development.

Question 3

Does graphql-elixir support GraphQL subscriptions?

Accepted Answer

Not directly in the core engine; subscriptions would require custom transport implementation, as it's transport-agnostic but doesn't include WebSocket or real-time handling out of the box.

Question 4

How to add authentication to a graphql-elixir schema?

Accepted Answer

Implement authentication in resolvers by passing context from the transport layer; for example, with plug_graphql, you can use Plug middleware to inject user data into the GraphQL execution context.

Question 5

Is graphql-elixir production ready?

Accepted Answer

It's used in production by some teams, but caution is advised due to missing features like directives. Check the project's status and version for updates on completeness and stability.

Question 6

How to handle errors in graphql-elixir resolvers?

Accepted Answer

Errors can be managed by returning {:ok, value} or {:error, message} tuples in resolvers, following Elixir conventions, and the execution engine will propagate them appropriately in the response.

graphql-elixir

What is graphql-elixir?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions