| .vscode | ||
| assets | ||
| config | ||
| lib | ||
| priv | ||
| test | ||
| .gitignore | ||
| go.sh | ||
| mix.exs | ||
| mix.lock | ||
| README.md | ||
Subscriptions
Our little React app is pretty neat. When it loads it queries the server for a list of people and shows their faces and allows us to run a mutation to add a new person to our list.
There's only one problem: what happens if someone else comes along and adds a face to our gallery? Our client won't know that the data has changed and will just keep showing us stale data. This is where GraphQL Subscriptions come in.
Absinthe has built-in support for subscriptions and since we're using Phoenix we have a well-tested channel implementation to run it over. Note that the GraphQL subscription specification is transport agnostic - Absinthe ships with it's own socket protocol as well as support for Phoenix's.
Notable changes:
lib/faces_web/endpoint.exlib/faces_web/schema/schema.exlib/faces_web/channels/user_socket.exassets/js/absinthe-socket-link.jsassets/js/client.jsassets/js/queries/person_added.jsassets/js/queries/list_people.js
Next, take a look at step-6.