best way to handle "complex" args #1162
Unanswered
chrisdrackett
asked this question in
General
Replies: 1 comment
-
curious if others are running into things like this. Even something simple like a mutation to update user settings gets messier than I would like:
the main thing I'm reacting to at this point is all the conditional spreads. I just don't see any other way to avoid wiping out these values when they are not passed in as part of the mutation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm curious if people have thoughts on the best way to handle args in nexus. For example I have the following code:
but I get an error like:
what is the best way to set something like this up? do I just need to add logic to handle
null
and/orundefined
?Beta Was this translation helpful? Give feedback.
All reactions