Vulcan in a Nutshell
The best way to understand how Vulcan works is to consider its three main aspects: the role of the schema, how Vulcan reads data, and how Vulcan writes data.
description, etc. describing a type of document (a movie, a post, a photo, a review, and so on).
The schema is what defines how a Collection (a.k.a. a Model) behaves, and it fulfills many important functions:
- It’s used to generate your GraphQL schema, which in turn controls your app’s GraphQL API.
- It’s used to control permissions.
- It’s used to generate forms.
Reading data basically means getting data from your database all the way to the user’s browser.
Let’s assume you have a
Movies.jsx component ready to take a
results prop and display its contents as a list of movies.
In order to pass that prop, you’ll wrap your component with the
withList higher-order component. You just need to specify the appropriate Collection, and optionally also specify a fragment to define which document fields to load.
MoviesList resolver will optionally check the query’s
terms argument and feed it through a set of callbacks in order to generate a valid MongoDB query, whose result it will return to
withList and from there back to your
Now let’s consider the opposite operation: writing data, such as editing a movie’s description.
First, you should know that the movie edit form can be automatically generated from your schema, meaning you don’t actually need to code it or worry about hooking it up to your GraphQL API.
EditMovies will then call a boilerplate mutator which will perform validation based on your schema, and finally modify the document inside your database.