cjoudrey/graphql-schema-linter

Warning instead of error?

Open

#239 opened on Jul 10, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (62 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (669 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This is more of a question than an issue, but curious if it's possible to do warns instead of errors, similar to how eslint structures their config.

Contributor guide

Research direction
Investigate how ESLint implements warn/error levels, then propose a similar configuration for graphql schema linter, focusing on rule severity.
Tech stack
javascriptgraphql
Domain
clitooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGraphQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60