Skip to content

Make issue level configurable #6516

@baconz

Description

@baconz

Use case

The specific use-case that raised this is:

  1. I have a project with deprecation warnings that are expected
  2. I have a server that is configured to fail on operations with unused variables

I would like the build to fail if there are unused variables, but not if there are deprecation warnings.

In slack, we discussed having full configurability on the level of each issue. Something like:

{ 
  issue: UnusedVariable,
  level: Error,
},
{ 
  issue: UnusedFragment,
  level: Warning,
},
{ 
  issue: DeprecatedUsage,
  level: Ignore,
},

Full slack thread is here.

Describe the solution you'd like

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions