-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
a/api/graphqla/data/postgresc/serverRelated to serverRelated to servere/hardWill take weeks of effortWill take weeks of effortk/enhancementNew feature or improve an existing featureNew feature or improve an existing featurep/mediumnon-urgent issues/features that are candidates for being included in one of the upcoming sprintsnon-urgent issues/features that are candidates for being included in one of the upcoming sprints
Description
Every field of a schema generated from SQL View is nullable/optional even though the underlying table might have NOT NULL fields that are NOT-nullable if the table we're tracked directly.
I've tested and found this problem on the alpha42 version.
This is a problem when working with statically typed languages such as ReasonML. You really don't want to spam option monad's map/flatmap if you don't need to. Basically, this ruins SQL views in a ReasonML / TypeScript (autogenerated types) setup entirely as suddenly everything is nullable.
drewwestphal, davetapley, mjonas87, petecorreia-appital, michael-land and 35 more
Metadata
Metadata
Assignees
Labels
a/api/graphqla/data/postgresc/serverRelated to serverRelated to servere/hardWill take weeks of effortWill take weeks of effortk/enhancementNew feature or improve an existing featureNew feature or improve an existing featurep/mediumnon-urgent issues/features that are candidates for being included in one of the upcoming sprintsnon-urgent issues/features that are candidates for being included in one of the upcoming sprints