absinthe-subscriptions
/absinthe-subscriptions
Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
- Author
- TheBushidoCollective ↗
- Repository
- han ↗
- Licence
- Apache-2.0
- Last repository change
- 08.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
Original author description
Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
How it works
- Key Concepts
- Best Practices
- PubSub Configuration
- Authorization in Subscriptions
- Anti-Patterns
SKILL.md preview
---
name: absinthe-subscriptions
user-invocable: false
description: Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
---
# Absinthe - Subscriptions
Guide to implementing real-time GraphQL subscriptions with Absinthe and Phoenix.
## Key Concepts
### Basic Setup
```elixir
# In your Phoenix endpoint
defmodule MyAppWeb.Endpoint do
use Phoenix.Endpoint, otp_app: :my_app
use Absinthe.Phoenix.Endpoint
socket "/socket", MyAppWeb.UserSocket,
websocket: true,
longpoll: false
end
# Socket configuration
defmodule MyAppWeb.UserSocket do
use Phoenix.Socket
use Absinthe.Phoenix.Socket, schema: MyApp.Schema
def connect(params, socket, _connect_info) do
current_user = get_user_from_token(params["token"])
socket = Absinthe.Phoenix.Socket.put_options(socket,
context: %{current_user: current_user}
)
{:ok, socket}
end
def id(socket), do: "user_socket:#{socket.assigns.user_id}"
end
```
### Defining Subscriptions
```elixir
defmodule MyApp.Schema.Subscriptions do
use Absinthe.Schema.Notation
object :post_subscriptions do
field :post_created, :post do
config fn _args, _resolution ->
{:ok, topic: "posts"}
end
trigger :create_post, topic: fn _post ->
"posts"
end
end
field :post_updated, :post do
arg :id, non_null(:id)
config fn %{id: id}, _resolution ->
{:ok, topic: "post:#{id}"}
end
trigger :update_post, topic: fn post ->
"post:#{post.id}"
end
end
end
end
```
### Publishing from Mutations
```elixir
defmodule MyApp.Resolvers.Post do
def create_post(_parent, %{input: input}, _resolution) do
case MyApp.Posts.create_post(input) do
{:ok, post} ->
# Publish to subscription
Absinthe.Subscription.publish(
MyAppWeb.Endpoint,
post,
post_created: "posts"
)
{:ok, post}
{:error, changeset} ->
{:error, changeset}
end
end
end
```
### User-Specific Subscriptions
```elixir
field :user_notification, :notification do
config fn _args, %{context: %{current_user: user}} ->
{:ok, topic: "user:#{user.id}:notifications"}
end
end
# Publishing
Absinthe.Subscription.publish(
MyAppWeb.Endpoint,
notification,
user_notification: "user:#{user_id}:notifications"
)
```
## Best Practices
1. **Scope subscriptions** - Use topics to limit data exposure
2. **Authenticate connections** - Verify users in socket connect
3. **Use triggers** - Automatically publish on mutations
4. **Handle disconnections** - Clean up resources on disconnect
5. **Rate limit subscriptions** - Prevent abuse
## PubSub Configuration
```elixir
# config/config.exs
config :my_app, MyAppWeb.Endpoint,
pubsub_server: MyApp.PubSub
# application.ex
children = [
{Phoenix.PubSub, name: MyApp.PubSub},
MyAppWeb.Endpoint,
{Absinthe.Subscription, MyAppWeb.Endpoint}
]
```
## Authorization in Subscriptions
```elixir
field :private_messages, :message do
config fn _args, %{context: context} ->
case context do
%{current_user: %{id: user_id}} ->
{:ok, topic: "user:#{user_id}:messages"}
_ ->
{:error, "Unauthorized"}
end
end
end
```
## Anti-Patterns
- Don't publish sensitive data to broad topics
- Avoid subscriptions without authentication
- Don't skip connection-level authorization
- Avoid overly granular topics (performance impact)
Versions
The database has no other skills named absinthe-subscriptions.
Database snapshot: 13.11.2026 · package version 21ebeb411340 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100absinthe-resolvers
Use when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling. - 100absinthe-schema
Use when designing GraphQL schemas with Absinthe. Covers type definitions, interfaces, unions, enums, and schema organization patterns. - 100phoenix-pubsub-patterns
Use when adding real-time updates to LiveViews with Phoenix.PubSub — scoped topics, broadcasting from contexts, handle_info with streams, Presence in LiveView. Not for raw WebSocket APIs (use phoenix-channels-essentials). - 100azure-web-pubsub-ts
Build real-time messaging applications using Azure Web PubSub SDKs for JavaScript (@azure/web-pubsub, @azure/web-pubsub-client). Use when implementing WebSocket-based real-time features, pub/sub me... - 100phoenix
Build and debug Phoenix web interfaces and HTTP endpoints. Use for LiveView lifecycle and data loading, components, forms, routes, controllers, Plug, channels, and PubSub. Use ecto for changesets, queries, and persistence behind those interfaces. - 100graphql-architect
Use when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.