getting the same behavior of null and undefined as in the query builder for generated queries

[halindraprakoso]

Hi,

I've been attempting to create a reusable update statement that utilizes optional parameters via edgeql codegen. Essentially, I'm aiming to replicate the behavior of the query builder; when I pass null, it sets a property to empty, while undefined leaves the property unchanged to prevent unwarranted mutation. However, I'm couldn't make it work since passing either null or undefined results in an empty set.

the following statement helps the latter but it's difficult to set the value to empty set

...
set {
    name: <optional str>$name ?? .name
}
...

unless if it's a str, I could still have a verbose workaround like this:

with
   n_email := <optional str>$email
...
set {
  email := ({} if n_email ?= ''  else (n_email ?? .email)) 
};

any ideas?