You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
name: Feature request
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''
---Describe the bug
Not a bug really, but it would be nice to be able to ignore certain lines/rules (such as how eslint does). In my project, the graphql was updated to deprecate some queries. This however meant that the front end pipeline was failing, as the warnings produced could not be ignored (they also throw an error code 1 despite only being warnings, not sure if this is on purpose)
To Reproduce
Steps to reproduce the behavior:
Try to use a deprecated query
Run validate command
Throws warning: The field *** is deprecated.
Expected behavior
Should be able to ignore the warning somehow while we transition to the new query
Thanks :)
The text was updated successfully, but these errors were encountered:
name: Feature request
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''
---Describe the bug
Not a bug really, but it would be nice to be able to ignore certain lines/rules (such as how eslint does). In my project, the graphql was updated to deprecate some queries. This however meant that the front end pipeline was failing, as the warnings produced could not be ignored (they also throw an error code 1 despite only being warnings, not sure if this is on purpose)
To Reproduce
Steps to reproduce the behavior:
Throws warning:
The field *** is deprecated.
Expected behavior
Should be able to ignore the warning somehow while we transition to the new query
Thanks :)
The text was updated successfully, but these errors were encountered: