-
I'm interested in proper support for custom scalar types. This has some overlap with the `enum` support mentioned in the readme, in particular this applies to them as well:
> However end users prob…
-
When using custom operations, the files generated doesn't include the import statements for custom scalars that have been defined.
Cikmo updated
2 months ago
-
Migrated from: apollographql/apollo-client#585
-
I want to store a mailing address in a single field. The best option I've found so far is to store it in a json field.
```
type Contact {
...
optional mailing_address: json;
...
}
`…
-
# Problem
Default scalars don't provide specific validation or convey the meaning for certain fields.
## Overview
WPGraphQL currently provides the following Scalars, based on the default Scala…
-
### Which packages are impacted by your issue?
@graphql-codegen/cli, @graphql-codegen/add, @graphql-codegen/typescript-operations, @graphql-codegen/typescript
### Describe the bug
https://codesandb…
-
Is it possible to use custom scalars for Graphql?
Is it activated in the project
-
Using the CLI option `--scalar`, it is possible to set the Typescript type of custom scalars. However, that only modifies the generated interfaces. The actual value of the scalar is unchanged.
For …
-
The spec for GraphQL allow for custom input scalars. This lib should allow custom input scalar.
This would allow the server implementation of graphql to catch a input scalar like ProductId(unsigned…
-
It would be useful if there would be a way to map certain primitive field scalars from certain types of the prisma schema to custom graphql scalars for example with [graphql-scalars](https://github.co…