Skip to content

Validate command does not log files that have only deprecations #2883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 4 tasks
HermanBilous opened this issue Apr 18, 2025 · 0 comments · May be fixed by #2884
Open
1 of 4 tasks

Validate command does not log files that have only deprecations #2883

HermanBilous opened this issue Apr 18, 2025 · 0 comments · May be fixed by #2884

Comments

@HermanBilous
Copy link

HermanBilous commented Apr 18, 2025

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

  • 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

    Make sure to fork this template and run pnpm generate in the terminal.

    Please make sure the Codegen and plugins version under package.json matches yours.

  • 2. A failing test has been provided
  • 3. A local solution has been provided
  • 4. A pull request is pending review

Describe the bug

  1. have a schema file e.g. schema.graphql
  2. have and operation file operation.graphql
  3. deprecate a field in schema and add it to a query in operation.graphql
  4. make sure that there are no errors in operation.graphql
  5. run graphql-inspector validate "operation.graphql" "schema.graphql"
  6. receive following output:
success All documents are valid
info 
Detected 1 document with deprecated fields:

To Reproduce Steps to reproduce the behavior:

Expected behavior
expected output:

success All documents are valid
info 
Detected 1 document with deprecated fields:

warn
in /Users/hermanbelous/Projects/vezha-public-frontend/o.graphql:


 - The field Post.field is deprecated. No longer supported

Environment:

  • OS: Osx
  • @graphql-inspector/5.0.8:
  • graphql:
  • NodeJS: 22

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant