Skip to content

# eslint-disable-next-line clashes with graphql-eslint's processor #153

@alecmev

Description

@alecmev

If I enable graphql-eslint's processor for Relay code, ESLint starts treating the GraphQL strings inside that code as standalone GraphQL files. That means eslint-plugin-relay is no longer enabled for them, if it's configured to match *.jsx or something. So when I try to use # eslint-disable-next-line relay/unused-fields I get Definition for rule 'relay/unused-fields' was not found from ESLint, which is expected behavior.

My current workaround is to add *.graphql to eslint-plugin-relay's files array, but that's suboptimal, as it's configuration bloat (and probably also has a runtime penalty). Not sure what's the best way to go about this, but using a processor, as suggested in #152, would help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions