kitten.sh
+5
.changeset/shiny-needles-arrive.md
+5
.changeset/shiny-needles-arrive.md
+3
-24
README.md
+3
-24
README.md
···you can opt into the object notation i.e. `{ "schema": { "url": "x", "headers": { "Authorization": "y" } }}`- `templateIsCallExpression` this tells our client that you are using `graphql('doc')` (default: true)unused fragments and provide a message notifying you about them (only works with call-expressions, default: true)- `trackFieldUsage` this only works with the client-preset, when turned on it will warn you about
···you can opt into the object notation i.e. `{ "schema": { "url": "x", "headers": { "Authorization": "y" } }}`- `templateIsCallExpression` this tells our client that you are using `graphql('doc')` (default: true)unused fragments and provide a message notifying you about them (only works with call-expressions, default: true)- `trackFieldUsage` this only works with the client-preset, when turned on it will warn you about+- `tadaOutputLocation` when using `gql.tada` this can be convenient as it automatically generates
+1350
-138
packages/example-tada/introspection.ts
+1350
-138
packages/example-tada/introspection.ts
···
···+'The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.',+'The `Int` scalar type represents non-fractional signed whole numeric values. Int can represent values between -(2^31) and 2^31 - 1.',+'The `ID` scalar type represents a unique identifier, often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"4"`) or integer (such as `4`) input value will be accepted as an ID.',+'The `Float` scalar type represents signed double-precision fractional values as specified by [IEEE 754](https://en.wikipedia.org/wiki/IEEE_floating_point).',+'A GraphQL Schema defines the capabilities of a GraphQL server. It exposes all available types and directives on the server, as well as the entry points for query, mutation, and subscription operations.',+'If this server support subscription, the type that subscription operations will be rooted at.',+'The fundamental unit of any GraphQL Schema is the type. There are many kinds of types in GraphQL as represented by the `__TypeKind` enum.\n\nDepending on the kind of a type, certain fields describe information about that type. Scalar types provide no information beyond a name, description and optional `specifiedByUrl`, while Enum types provide their values. Object and Interface types provide the fields they describe. Abstract types, Union and Interface, provide the Object types possible at runtime. List and NonNull types compose other types.',+'Indicates this type is an interface. `fields`, `interfaces`, and `possibleTypes` are valid fields.',+'Object and Interface types are described by a list of Fields, each of which has a name, potentially a list of arguments, and a return type.',+'Arguments provided to Fields or Directives and the input fields of an InputObject are represented as Input Values which describe their type and optionally a default value.',+'One possible value for a given Enum. Enum values are unique values, not a placeholder for a string or numeric value. However an Enum value is returned in a JSON response as a string.',+"A Directive provides a way to describe alternate runtime execution and type validation behavior in a GraphQL document.\n\nIn some cases, you need to provide options to alter GraphQL's execution behavior in ways field arguments will not suffice, such as conditionally including or skipping a field. Directives provide this by describing additional information to the executor.",+'A Directive can be adjacent to many parts of the GraphQL language, a __DirectiveLocation describes one such possible adjacencies.',+'Directs the executor to include this field or fragment only when the `if` argument is true.',+'Explains why this element was deprecated, usually also including a suggestion for how to access supported similar data. Formatted using the Markdown syntax, as specified by [CommonMark](https://commonmark.org/).',
+2
packages/example-tada/src/index.tsx
+2
packages/example-tada/src/index.tsx
+2
-1
packages/example-tada/tsconfig.json
+2
-1
packages/example-tada/tsconfig.json
+3
-22
packages/graphqlsp/README.md
+3
-22
packages/graphqlsp/README.md
···unused fragments and provide a message notifying you about them (only works with call-expressions, default: true)- `trackFieldUsage` this only works with the client-preset, when turned on it will warn you about
···unused fragments and provide a message notifying you about them (only works with call-expressions, default: true)- `trackFieldUsage` this only works with the client-preset, when turned on it will warn you about+- `tadaOutputLocation` when using `gql.tada` this can be convenient as it automatically generates
+41
packages/graphqlsp/src/graphql/getSchema.ts
+41
packages/graphqlsp/src/graphql/getSchema.ts
···············
···············
+7
packages/graphqlsp/src/index.ts
+7
packages/graphqlsp/src/index.ts
·········
·········