Giter VIP home page Giter VIP logo

graphlint's Introduction

GraphLint

A linting tool for GraphQL schemas.

This tool is meant for finding errors in your GraphQL schemas. It is not made for your Queries. The tool contains multiple inspections which can be added to the user's config file for checking for different things. The purpose of this tool is to implement the GraphQL Standard from Worksome.

Installation

The tool can be installed as a composer global dependency via

$ composer global require worksome/graphlint

or via Homebrew

brew tap worksome/tap
brew install --formula worksome/tap/graphlint

Usage

The tool can be run via

$ graphlint path/to/schema.graphql

CI Usage with GitHub Actions

With GitHub Actions, we support using the cs2pr tool to add inline annotations to your pull requests.

graphlint --format=checkstyle path/to/schema.graphql | cs2pr

Configuration

โš ๏ธ Currently the package only supports running on compiled schema. It will later get support for running on original schemas also.

Create a file in the root called graphlint.php with the following configuration.

<?php declare(strict_types=1);

use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
use Worksome\Graphlint\Configuration\Visitor;
use Worksome\Graphlint\Inspections\CamelCaseFieldDefinitionInspection;

return function (ContainerConfigurator $config): void {
    $services = $config->services();

    $services->set(CamelCaseFieldDefinitionInspection::class)
        ->tag(Visitor::COMPILED);
};

To use the Worksome GraphQL standard:

<?php declare(strict_types=1);

use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
use Worksome\Graphlint\GraphlintSet;

return function (ContainerConfigurator $config): void {
    $config->import(GraphlintSet::Standard->value);
};

The tool can have a configuration for schemas before compiling and after. Some libraries do not compile their schema, so for those only one of the tags should be used.

Ignoring problems

A problem can be suppressed by adding an ignore-next-line comment before it.

interface Account {
    # @graphlint-ignore-next-line
    id: ID
}

In some cases, it is not possible to add a comment because the schema is auto generated. For those cases, the error can be ignored by adding the following in the configuration file.

return function (ContainerConfigurator $config): void {
    $config->services()
        ->set(IgnoreByNameSuppressorInspection::class)
        ->call('configure', [
            'TEST',
            'AccountInput.name' // Dotted value for only applying on some fields
        ]);
};

Testing

This package ships with a docker configuration for running the tests. Assuming you have cloned the repository and have docker and docker-compose installed, you can run the tests by running

docker-compose run --rm composer install # Only needed the first time
docker-compose run --rm pest

graphlint's People

Contributors

dependabot[bot] avatar lukeraymonddowning avatar olivernybroe avatar owenvoke avatar spawnia avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

graphlint's Issues

Only apply NonNullableListInspection to output types

I ran an inspection on our schema and added NonNullableListInspection. It found many issues in our schema where non-nullable lists are used in input types, which I think is fine and not against the spirit of the rule:

 input UpdateWgsSvEventHasMany {
-  create: [CreateWgsSvEventInput!]
-  update: [UpdateWgsSvEventInput!]
-  delete: [ID!]
+  create: [CreateWgsSvEventInput!]!
+  update: [UpdateWgsSvEventInput!]!
+  delete: [ID!]!
 }

It would be nice if the rule only applied to output types - or were made configurable to allow this.

Look into schema traversing instead of AST traversing

Currently we traverse the AST, however the graphql library has another higher level type it can create called a Schema which is a parsing of the AST.

We should look into if we are able to traverse that instead of the AST or if we can parse the schema to the AST traversing for allowing to see this extra information.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.