graphql / graphql/graphql-spec
More scalar types (`BigInt`, `Char`, `Arrays`, ...)
- Dominant language
- JavaScript
- Stars
- 14.6k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
As systems grow across multiple DB infrastructures we need to be able to ensure data correctness. This can not be done without having a wider set of standard data types in GraphQL. Right now the developer has to add custom types but the developer is usually the weakest link in the system and a simple oversight that would be caught by a type checker can cost millions if we don't have that data type to begin with or isn't configured right. A missing value in an array could offset the contents of a variable causing the wrong data to be stored in a field.
The most useful ones I can think of right now
- BigInt (MYSQL might pass you a int you can't store)
- Double (Important when dealing with money)
- Char (setting genders or storing state abbreviations or foreign postal codes)
- Long/Blob (content and file storage)
- Unique / Auto increment / generated UUIDs
- Multi dimensional Arrays
- Associative Arrays
- Date/Time (most important generating timestamps using server time)
I am sure there are more that are important but I think these are the most commonly used. Which is another reason they should be included instead of everyone having to add them themselves.
Contributor guide
Assessment
This issue has not been assessed yet.