Product
:Int
, Float
, String
, Boolean
and ID
. Scalar types, as opposed to object types, point to actual data. The ID
type resolves to a string, but expects a unique value.Category
enum type can take a value of Clothes
, Shoes
or Watches
and anything else will result in a validation error. We need to update our example providing definition of our enumeration category : !
and [β¦]
. Hereβs a breakdown, using the String
scalar type as an example:String
: nullable string (the resolved value can be null)String!
: Non-nullable string (if the resolved value is null, an error will be raised) [String]
: Nullable list of nullable string values. The entire value can be null, or specific list elements can be null. [String!]
: Nullable list of non-nullable string values. Then entire value can be null, but specific list elements cannot be null. [String!]!
: Non-nullable list of non-nullable string values. Nothing can be null, neither the whole value nor the individual items. incrementCredits
mutations in one request, the first is guaranteed to finish before the second begins, ensuring that we don't end up with a race condition with ourselves.