Releases: 0no-co/GraphQLSP
Releases · 0no-co/GraphQLSP
@0no-co/graphqlsp@0.4.1
Patch Changes
- Optimise parse performance by omitting location information
Submitted by @JoviDeCroock (See660235e
) - Improve the error-codes so they become discernible
Submitted by @JoviDeCroock (See8f3de11
)
@0no-co/graphqlsp@0.4.0
Minor Changes
- Add a
message
diagnostic when we see an import from a file that hasfragment
exports we'll warn you when they are not imported, this because of the assumption that to use this file one would have to adhere to the data requirements of said file.
You can choose to disable this setting by settingshouldCheckForColocatedFragments
tofalse
Submitted by @JoviDeCroock (See #42)
@0no-co/graphqlsp@0.3.0
Minor Changes
- only run the
typescript
plugin once to generate a set of types that we'll reference from our
typescript-operations
, this to reduce lengthy generated files
Submitted by @JoviDeCroock (See #39)
@0no-co/graphqlsp@0.2.1
Patch Changes
- Bump the graphql-code-generator and graphiql-utils dependencies
Submitted by @JoviDeCroock (See #35)
0.2.0
Minor Changes
- Add ability to specify a URL for your schema, GraphQLSP will then fetch the introspection from the specified URL
Submitted by @JoviDeCroock (See #26) - Display some documentation alongside fields and fragments, for fields it will show the documentation or the type and for fragmentSpreads the typeCondition will be displayed
Submitted by @JoviDeCroock (See #31)
Patch Changes
- Check the
dirty
state of the file an additional time to prevent writing to the file when the user types directly after saving
Submitted by @JoviDeCroock (See #27) - Enforce the correct type on FragmentSpread suggestions
Submitted by @JoviDeCroock (See #32)