Optional type with setter #185
niklaswallerstedt
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Trying out ElectroDB together with SST, looks really promising!
I'm having some issue with the
createdAt
/updatedAt
examples, as the return type isnumber | undefined
. This requires me to check that there is a value in the api or application layer before returning a response with graphql.Is there some way to say that an attribute always will be present, without also introducing it in
.create()
?ElectroDB playground link
Related: #184
Beta Was this translation helpful? Give feedback.
All reactions