Skip to content

Releases: dimaMachina/graphql-eslint

July 31, 2024

31 Jul 22:49
aa5df74
Compare
Choose a tag to compare
July 31, 2024 Pre-release
Pre-release

@graphql-eslint/[email protected]

Patch Changes

  • #2455
    08a8a13
    Thanks @dimaMachina! - fix caching issues for
    no-unreachable-types / no-unused-fields rules for multi projects

  • #2458
    9096458
    Thanks @dimaMachina! - add meta object with name and
    version to parser and processor to be compatible with ESLint 9

July 29, 2024

29 Jul 18:26
76aeed0
Compare
Choose a tag to compare
July 29, 2024 Pre-release
Pre-release

@graphql-eslint/[email protected]

Major Changes

August 29, 2023

29 Aug 17:53
d4c236f
Compare
Choose a tag to compare
August 29, 2023 Pre-release
Pre-release

@graphql-eslint/[email protected]

Major Changes

  • #1794
    4079167e
    Thanks @B2o5T! - - bring back possible-type-extension rule to
    schema-recommended config

    • add unique-operation-name and unique-fragment-name rules to operations-recommended config

    The concept of sibling operations provided by graphql-config's documents fields is based on
    uniquely named operations and fragments, for omitting false-positive/negative cases when
    operations and fragments are located in separate files. For this reason, these rules must be
    included in the recommended config

    • rename relay config to schema-relay

    To avoid confusing when users extend this config for executable definitions (operations and
    fragments)

  • #1812
    bf475e88
    Thanks @B2o5T! - - alphabetize rule changes

    • add definitions: true option for schema-all/operations-all configs

    • rename values: ['EnumTypeDefinition'] to values: true

    • rename variables: ['OperationDefinition'] to variables: true

    • add groups: ['id', '*', 'createdAt', 'updatedAt'] for schema-all/operations-all configs

    • require-id-when-available rule changes

      • rename rule to require-selections
    • update schema-all/operations-all configs

    • require-description rule changes

      • add rootField: true option for schema-recommended config
    • require eslint at least >=8.44.0 as peerDependency

    • naming-convention

      • add new options for schema-recommended config
      {
        'EnumTypeDefinition,EnumTypeExtension': {
          forbiddenPrefixes: ['Enum'],
          forbiddenSuffixes: ['Enum']
        },
        'InterfaceTypeDefinition,InterfaceTypeExtension': {
          forbiddenPrefixes: ['Interface'],
          forbiddenSuffixes: ['Interface']
        },
        'UnionTypeDefinition,UnionTypeExtension': {
          forbiddenPrefixes: ['Union'],
          forbiddenSuffixes: ['Union']
        },
        'ObjectTypeDefinition,ObjectTypeExtension': {
          forbiddenPrefixes: ['Type'],
          forbiddenSuffixes: ['Type']
        }
      }
    • remove graphql-js' unique-enum-value-names rule

    • rename no-case-insensitive-enum-values-duplicates to unique-enum-value-names

      Since this rule reports case-insensitive enum values duplicates too

    • require-nullable-result-in-root rule changes

      Do not check subscriptions

  • #1795
    2f46a717
    Thanks @B2o5T! - - remove parserOptions.schema

    • remove parserOptions.documents

    • remove parserOptions.extensions

    • remove parserOptions.include

    • remove parserOptions.exclude

    • remove parserOptions.projects

    • remove parserOptions.schemaOptions

    • remove parserOptions.graphQLParserOptions

    • remove parserOptions.skipGraphQLConfig

    • remove parserOptions.operations

    • add parserOptions.graphQLConfig?: IGraphQLConfig for programmatic usage

  • #1793
    6593482b
    Thanks @B2o5T! - drop support of Node.js 12/14/16, GraphQL 14/15

  • #1792
    804f8b61
    Thanks @B2o5T! - Remove GraphQLRuleTester from bundle, to test your
    rules use regular RuleTester from eslint

    Note: with this change unnecessary dependency @babel/code-frame was removed too

    import { RuleTester } from 'eslint'
    
    const ruleTester = new RuleTester({
      parser: require.resolve('@graphql-eslint/eslint-plugin')
    })

Patch Changes

July 13, 2023

13 Jul 07:23
ba9f4aa
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Patch Changes

  • #1750
    7b461a1
    Thanks @B2o5T! - ESLint configuration in ... is invalid. Unexpected
    top-level property "default". Fix targeting for legacy Node.js versions

July 04, 2023

04 Jul 10:39
99bdd63
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Minor Changes

  • #1729
    018b2da
    Thanks @B2o5T! - bundle with tsup to strip out development code, check
    with bob

July 02, 2023

02 Jul 10:10
964fb2f
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Patch Changes

  • #1725
    5f3f1a5
    Thanks @B2o5T! - fix
    Parsing error: Cannot read properties of undefined (reading '0') eslint in VSCode

June 30, 2023

30 Jun 23:37
f32b861
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Patch Changes

May 23, 2023

23 May 17:03
ac5e344
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Patch Changes

  • #1665
    73b1087
    Thanks @B2o5T! - fix
    TypeError: Cannot read properties of undefined (reading 'kind') for
    require-nullable-result-in-root rule

May 22, 2023

22 May 19:54
519877f
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Minor Changes

  • #1657
    0a571bb
    Thanks @nishtahir! - Add require-nullable-result-in-root rule to
    report on non-null fields in root types

March 28, 2023

28 Mar 22:43
e4bdbfe
Compare
Choose a tag to compare

@graphql-eslint/[email protected]

Minor Changes