Skip to content
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

bit.ly links broken? #2312

Open
4 tasks
benjie opened this issue May 13, 2024 · 0 comments
Open
4 tasks

bit.ly links broken? #2312

benjie opened this issue May 13, 2024 · 0 comments

Comments

@benjie
Copy link

benjie commented May 13, 2024

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

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

    For example, you can start off by editng the
    'basic' example on Stackblitz.

    Please make sure the graphql-eslint 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

When you have a lint configuration error such as:

ESLint: 8.57.0

Error: Rule `known-fragment-names` requires `parserOptions.operations` to be set and loaded. See https://bit.ly/graphql-eslint-operations for more info
Occurred while linting /home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/packages/api/__tests__/integration/process.graphql.ts/2_document.graphql:1
Rule: "@graphql-eslint/known-fragment-names"
    at requireSiblingsOperations (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/@graphql-eslint+eslint-plugin@3.20.1_patch_hash=ewoknrusd6bn2smrwwxki7qdgy_@babel+core@7.24.5_dm6bygupuzqzpfwg5kzk4r6edm/node_modules/@graphql-eslint/eslint-plugin/cjs/utils.js:57:11)
    at handleMissingFragments (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/@graphql-eslint+eslint-plugin@3.20.1_patch_hash=ewoknrusd6bn2smrwwxki7qdgy_@babel+core@7.24.5_dm6bygupuzqzpfwg5kzk4r6edm/node_modules/@graphql-eslint/eslint-plugin/cjs/rules/graphql-js-validation.js:97:65)
    at Document (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/@graphql-eslint+eslint-plugin@3.20.1_patch_hash=ewoknrusd6bn2smrwwxki7qdgy_@babel+core@7.24.5_dm6bygupuzqzpfwg5kzk4r6edm/node_modules/@graphql-eslint/eslint-plugin/cjs/rules/graphql-js-validation.js:159:52)
    at ruleErrorHandler (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/linter.js:1076:28)
    at /home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/node-event-generator.js:297:26)
    at NodeEventGenerator.applySelectors (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/node-event-generator.js:326:22)
    at NodeEventGenerator.enterNode (/home/benjie/Dev/gosteelhead/steelhead-deploy/gosteelhead/node_modules/.pnpm/eslint@8.57.0/node_modules/eslint/lib/linter/node-event-generator.js:340:14)

the URL https://bit.ly/graphql-eslint-operations links to https://github.com/dimaMachina/graphql-eslint#extended-linting-rules-with-siblings-operations which has no relevant information

To Reproduce Steps to reproduce the behavior:

Visit https://bit.ly/graphql-eslint-operations

Expected behavior

See documentation related to this error.

Environment:

  • OS: Ubuntu 22.04
  • @graphql-eslint/eslint-plugin: 3.20.1
  • Node.js: 20.12.1

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

No branches or pull requests

1 participant