Skip to content

chore(deps): update dependency eslint to v9 #3940

chore(deps): update dependency eslint to v9

chore(deps): update dependency eslint to v9 #3940

GitHub Actions / GraphQL Inspector succeeded Sep 20, 2024 in 1s

Everything looks good

Found 4 changes

Breaking: 0
Dangerous: 4
Safe: 0

Dangerous changes

  • Field title (deprecated) was removed from object type Post
  • Field Post.createdAt changed type from String to String!
  • Field Post.modifiedAt changed type from String to String!
  • Argument id: ID added to field Query.post

Looking for more advanced tool? Try GraphQL Hive!

Annotations

Check warning on line 3 in example/schemas/schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'title' (deprecated) was removed from object type 'Post'

Removing a deprecated field is a breaking change. Before removing it, you may want to look at the field's usage to see the impact of removing the field.

Check warning on line 8 in example/schemas/schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'Post.createdAt' changed type from 'String' to 'String!'

Field 'Post.createdAt' changed type from 'String' to 'String!'

Check warning on line 9 in example/schemas/schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Field 'Post.modifiedAt' changed type from 'String' to 'String!'

Field 'Post.modifiedAt' changed type from 'String' to 'String!'

Check warning on line 13 in example/schemas/schema.graphql

See this annotation in the file changed.

@github-actions github-actions / GraphQL Inspector

Argument 'id: ID' added to field 'Query.post'

Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.