Setting custom parameters to null vs empty is confusing

[mpawliszyn]

If a value is ever touched it will use empty string rather than null as the value. There is no way to unset it afaik either.

Not quite sure what we should do here. We could have a null checkbox that starts out checked. But that seems like overkill.

Another option is to treat empty as null but this isn't great either. Maybe someone else has a better idea.

[shellderp]

oh yeah... I ran into this before. it is tricky..

the only other idea I had was to have only nonnullable parameter boxes visible at the start (we'd need to add a "required" flag ..) and a "add" button to add nullable parameters, that would add the input field and a blank one would be emptystring, to null it out you just click x to remove it

I'm ok with a null checkbox too

[mpawliszyn]

I sort-of like the idea of telling Backfila when a parameter is required. Although having something be required and then accepting empty string might not be enough to fix confusion? Maybe it is.

I guess that add button would contain the remaining set of parameters.

All this UI dev, not sure my brain can handle it anymore 😛