Skip to content

ESLint directives are broken? #8

Open
@dimaMachina

Description

@dimaMachina

Describe the bug

I just did a setup for extracting vue and svelte <script>'s and found a similar case that ESLint's directives are broken. Are there any tests to unsure that eslint directive works? Or is it an issue with graphql-eslint?

Reproduction

https://github.com/dimaMachina/graphql-eslint/tree/better-vue-processor/examples/vue-code-file

System Info

System:
    OS: macOS 13.4
    CPU: (12) x64 Apple M2 Max
    Memory: 7.01 GB / 96.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - ~/.local/state/fnm_multishells/22235_1732128352787/bin/node
    npm: 10.9.0 - ~/.local/state/fnm_multishells/22235_1732128352787/bin/npm
    pnpm: 9.14.1 - ~/.local/state/fnm_multishells/22235_1732128352787/bin/pnpm
    Watchman: 2024.08.05.00 - /usr/local/bin/watchman
  Browsers:
    Chrome: 128.0.6613.114
    Safari: 16.5

Used Package Manager

pnpm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions