You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, one has to define the type for postgres, graphql and typescript explicitly like @Column({ type: "integer", gqlType: "Int" }) public count: number;.
Basic types like, numberstringboolean or any might be detected automatically using reflections and the postgres and graphql types will be set respectively. In contrasts, if the types do not match up, e.g. @Column({ type: "boolean", gqlType: "Int" }) public name: string;,, warnings or errors can be logged or thrown.
The text was updated successfully, but these errors were encountered:
Package
Description / Use Case for a Feature
Currently, one has to define the type for postgres, graphql and typescript explicitly like
@Column({ type: "integer", gqlType: "Int" }) public count: number;
.Basic types like,
number
string
boolean
orany
might be detected automatically using reflections and the postgres and graphql types will be set respectively. In contrasts, if the types do not match up, e.g.@Column({ type: "boolean", gqlType: "Int" }) public name: string;
,, warnings or errors can be logged or thrown.The text was updated successfully, but these errors were encountered: