question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`graphql-js` warning

See original GitHub issue

Describe the bug

I think it’s isn’t a bug, but just a misconfiguration from my side. I’ve tried to find a solution for this in a bunch of places without luck. Decided to open an issue to try to find out more.

These are happening:

warning [graphql-eslint] You rule "unique-input-field-names" depends on a GraphQL validation rule "UniqueInputFieldNames" but it's not available in the "graphql-js" version you are using. Skipping...
warning [graphql-eslint] You rule "unique-variable-names" depends on a GraphQL validation rule "UniqueVariableNames" but it's not available in the "graphql-js" version you are using. Skipping...
warning [graphql-eslint] You rule "value-literals-of-correct-type" depends on a GraphQL validation rule "ValuesOfCorrectType" but it's not available in the "graphql-js" version you are using. Skipping...
warning [graphql-eslint] You rule "variables-are-input-types" depends on a GraphQL validation rule "VariablesAreInputTypes" but it's not available in the "graphql-js" version you are using. Skipping...

To Reproduce Steps to reproduce the behavior:

My configuration:

"overrides": [
    {
      "files": ["*.ts", ".tsx"],
      "processor": "@graphql-eslint/graphql"
    },
    {
      "files": ["*.graphql"],
      "extends": "plugin:@graphql-eslint/operations-recommended",
      "rules": {
        "@graphql-eslint/unique-fragment-name": "error",
        "@graphql-eslint/naming-convention": "warn"
      },
      "parserOptions": {
        "operations": ["./src/**/*.graphql", "./src/**/*.{ts,tsx}"],
        "schema": "../backend/src/graphql/schema.generated.graphql"
      }
    }
  ]

Expected behavior no warnings

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:2
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
lhrinaldicommented, Mar 24, 2022

Makes a lot of sense! Thanks for clarifying.

1reaction
B2o5Tcommented, Mar 24, 2022

Hi, which version of graphql-js are you using?

Read more comments on GitHub >

github_iconTop Results From Across the Web

GraphQL: how can I throw a warning after a successful ...
What I'd like to implement is a middle scenario, where the mutation succeeds (returning a Post ); but also somehow returns a warning...
Read more >
GraphQL - Alert mutation rule - How to set the warning level?
Hello,. Do you know if it is possible to configure a mutation rule in graphQL that sets the warning threshold?
Read more >
Warning when use GraphQLNonNull or GraphQLList #2338
The official graphql-js document refers that GraphQLNonNull is a class so if I want to use it I have to instantiate it and...
Read more >
Handling operation errors - Apollo GraphQL Docs
Apollo Client can encounter a variety of errors when executing operations on your GraphQL server. Apollo Client helps you handle these errors according...
Read more >
Heuristic Fragment matcher warning! How to fix it?
Before you freak out why this warning occurs, understand the fact that Apollo Client doesn't know our GraphQL schema and hence it cannot...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found