Replies: 1 comment 2 replies
-
I was able to solve nickname and email check by replacing it with I don't quite like it though. Is this the best solution? Having some null/none value as default would be better here. but I did not find anything in docs. Empty sets will not work because of the way the are compared. EDIT: after doing this 2nd problem returned. Function only works correctly with both arguments. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have this function:
nickname
andemail
parameters are optional because there are a few contexts where they will require additional query to fetch.I have a few questions:
(.nickname != <str>{} OR .email != <str>{})
is this the correct way of checkingoptional
values?Actually this happens:
email type has regex constraint requiring
@
, but this constraint is ignored in the 1st case and seems like nothing gets executed because function returns empty set.EDIT: now this works for some reason, not sure if I even changed anything.
Full schema: https://gist.github.com/Fogapod/95bce022040e039843fea0d9ae233a89
Beta Was this translation helpful? Give feedback.
All reactions