@0no-co/graphqlsp@1.3.0

Minor Changes

• Support array destructuring result lists
  Submitted by @JoviDeCroock (See #204)

@0no-co/graphqlsp@1.2.0

Minor Changes

• support property assignment/objectAccessPattern
  Submitted by @JoviDeCroock (See #202)

@0no-co/graphqlsp@1.1.2

Patch Changes

• Automatically disable Prettier and ESLint on tadaOutputLocation output files
  Submitted by @kitten (See #199)

@0no-co/graphqlsp@1.1.1

Patch Changes

• Add @_unmask to known client directive list
  Submitted by @kitten (See #197)

@0no-co/graphqlsp@1.1.0

Minor Changes

• Add way to provide additional reserved keys for field-usage tracking by means of the reservedKeys config property which accepts an array of strings
  Submitted by @JoviDeCroock (See #195)

@0no-co/graphqlsp@1.0.7

Patch Changes

• Avoid bailing out of the cache for identical introspections
  Submitted by @JoviDeCroock (See #193)
• Account for empty lines when asking for completions
  Submitted by @JoviDeCroock (See #191)

@0no-co/graphqlsp@1.0.6

Patch Changes

• Catch errors in field-usage as we have been seeing TS fail to resolve references
  Submitted by @JoviDeCroock (See #188)

@0no-co/graphqlsp@1.0.5

Patch Changes

• When creating a d.ts file, export the introspection type to make it reusable
  Submitted by @kitten (See #184)
• Upgrade to @urql/introspection@1.0.3
  Submitted by @kitten (See #185)

@0no-co/graphqlsp@1.0.4

Patch Changes

• When we have a query like the following

  query {
    pokemon(id: 1) {
      id
      name
    }
    pokemons {
      id
      fleeRate
    }
  }

  and we perform

  const Pokemons = () => {
    const [result] = useQuery({
      query: PokemonQuery,
    });
  
    return result.data.pokemons.map(pokemon => pokemon.fleeRate);
  };

  Then it will see pokemon the variable inside our function closure as an
  allowed field due to Query.pokemon this PR fixes that by refining our search
  algorithm to only include valid built paths.
  Submitted by @JoviDeCroock (See #182)

@0no-co/graphqlsp@1.0.3

Patch Changes

• Stop caching diagnostics for fragment imports and field-usage as these can be controlled externally
  Submitted by @JoviDeCroock (See #174)
• Add fix for nonNullAssertion and using Array.at
  Submitted by @JoviDeCroock (See #177)