When it comes to writing code collaboratively, consistency is everything. APIs are no exception. In fact, APIs are perhaps the most important place to ensure consistency, since they act as a vein for collaboration across nearly every developer in an organization’s ecosystem.
For GraphQL APIs, the schema is at the heart of all collaboration and consumption, but ensuring consistency in a graph that spans many teams, tools, and workflows is no easy task. Today, we’re excited to make things a bit easier by adding schema linting to Apollo GraphOS!
As an API platform owner, linter checks in GraphOS will help you keep your schema syntax clean and consistent by validating that schema changes pass pre-defined formatting and naming rules like:
- Field names should be
- Input type names should be suffixed with
@tagdirective should use a pre-approved value for its
Starting today, schema linting is available for all orgs on the GraphOS Enterprise and Serverless plans. Linter checks will automatically run whenever new schema changes are published to GraphOS, but you can also run checks manually on a local schema or in a separate CI/CD pipeline using the Rover CLI.
Consistency at every stage of graph development
GraphOS schema linting is designed to integrate seamlessly into your existing processes to ensure that your schema’s syntax stays consistent at every stage of graph development.
Lint locally with the Rover CLI
No one wants to reread all of the code they just wrote to figure out where they miscapitalized one field. Using the Rover CLI, devs can run schema linting on their local schema as they work to ensure that their changes pass when published.
Integrate into CI/CD
Linting locally helps individual developers work quickly, but keeping a cross-team code base consistent requires enforcing linter rules centrally. Similar to other linting tools you may use, GraphOS schema linting can be integrated directly into your existing CI/CD pipelines to ensure that every schema change is checked before being published, no matter who it comes from.
To run schema linting in a third-party CI/CD tool, just install the Rover CLI as part of your pipeline.
Linter checks on published schemas in GraphOS
GraphOS gives you a central source of truth for all of your schemas and, if you have a federated graph, acts as the final checkpoint for your schema before your graph router uses it in production.
Running linter checks for new changes published to your schema in GraphOS ensures consistency in all of your running graphs.
If you already have schema checks set up in GraphOS, linter checks will automatically be added to your checks workflow! You can review the status of linter checks on the checks page in GraphOS Studio.
Configuring the linter in GraphOS Studio
The linter in GraphOS comes with a pre-defined list of rules that cover common best practices for writing GraphQL schemas. You can customize the severity of each rule independently to
Error in GraphOS Studio under Checks > Configuration > Linter.
When set to
Warn, a rule violation will allow the checks workflow to pass but output a warning, whereas a violation of a rule set to
Error will cause the checks workflow to fail outright.
You can also choose to have the linter ignore definitions marked with
@inaccessible to prevent errors caused by outdated or private definitions.
Starting today, linting is enabled for every organization on GraphOS Enterprise and Serverless plans. All you need to do to get started is publish a change to your graph! If you have schema checks enabled, you’ll automatically see linter checks as a new step.
If you want to change the linter configuration for your graph, head to the “Checks” tab in GraphOS Studio → Configuration → Linter. Or if you haven’t set up schema checks yet for your graph, check out the documentation to get started.
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.
Make this article better!
Was this post helpful? Have suggestions? Consider so we can improve it for future readers ✨.