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 (669 stars) (62 forks)batch import
enhancementhelp wanted

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

Tech stack
javascript
Domain
toolingdeveloper experience
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how eslint implements warn vs error severity (e.g., using a 'severity' property in rule config). Examine the graphql schema linter source code to understand how rules are defined and errors are reported. Look at existing comments in the issue for any prior discussion. Propose a design to add a 'severity' option to the rule configuration and modify the linter to output warnings accordingly.