Skip to main content

Is there some recommended way to handle/distinguish between unprovided data (null/undefined) and empty data (empty string) while developing custom actions?

Endpoint handles not-provided data as “no not change” and provided data as “change” and empty strings are valid values. I can, of course, do it by having a boolean field next to every data field, but it feels too nasty...

Be the first to reply!

Reply