Releases: 0no-co/GraphQLSP
Releases · 0no-co/GraphQLSP
@0no-co/[email protected]
Minor Changes
- Support array destructuring result lists
Submitted by @JoviDeCroock (See #204)
@0no-co/[email protected]
Minor Changes
- support property assignment/objectAccessPattern
Submitted by @JoviDeCroock (See #202)
@0no-co/[email protected]
@0no-co/[email protected]
@0no-co/[email protected]
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/[email protected]
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/[email protected]
Patch Changes
- Catch errors in field-usage as we have been seeing TS fail to resolve references
Submitted by @JoviDeCroock (See #188)
@0no-co/[email protected]
Patch Changes
- When creating a
d.ts
file, export the introspection type to make it reusable
Submitted by @kitten (See #184) - Upgrade to
@urql/[email protected]
Submitted by @kitten (See #185)
@0no-co/[email protected]
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 toQuery.pokemon
this PR fixes that by refining our search
algorithm to only include valid built paths.
Submitted by @JoviDeCroock (See #182)
@0no-co/[email protected]
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)