Empty Inputs not NULL after typing in them/removing characters

[japerry911]

Describe the issue

I have a STRING type input, Property IDs.
It defaults to NULL since I have required: false , but if I accidentally type in it, and delete what I type, it ends up going through as an empty string "".
I was curious, is there a way to make it NULL instead of empty string when you revert what's inputted? My use case is I use Pebble expression to remove --property_ids <property_ids_input from a Python script call if Property IDs is NULL. I could always remove if NULL or empty string, but I wanted to check before doing that.
let me know if you need more details in responding to this, appreciate the help, thank you

Images:
1st image shows input as it appears after I delete text that accidentally inputted
2nd image shows input in execution overview tab showing Blank string and not NULL

Environment

• Kestra Version: v0.16.6
• Operating System (OS/Docker/Kubernetes): GCP VM Docker Compose
• Java Version (if you don't run kestra in Docker): n/a

[anna-geller]

You can close the window and reopening again will no longer have that empty string;)

Alternatively, what if you explicitly type null without any quotes? AFK so hard to check atm

[japerry911]

I'll test typing 'null' when I get back.

I was thinking there could be a little null button or something like the checkboxes have above input box or something. I'll elaborate when I get on later.

Thanks @anna-geller !

[japerry911]

Alternatively, what if you explicitly type null without any quotes?

This does not work, does "null" as string.

I was envisioning something like this, where you could press None, or String and if String it gives input box.

*This is not blocking anything for me, so nothing urgently needs to be done on it, just noticed it when I was 'deving' and rerunning runs frequently.

[loicmathieu]

@anna-geller it's not a bug and providing a specific UI for such thing may be a bit overkilled. Let's move this to 0.18 to have more time to think about it.

[anna-geller]

we discussed together that an input should never be an empty string so we'll replace the empty string input values with null on the UI-side — @MilosPaunovic ping me if you want more details/examples