Optional in json schema are shown with both "null" and the actual type under the Optional

[brian-mulier-p]

Describe the issue

tbh idk if it's worth anytime but at least it's tracked feel free to close if you're ok to live with that, I am

If any change has to be made, basically the type property of the json schema is returned as an array as ["null", "string"] for eg. then it's parsed and displayed as-is in ui-libs.

Basically it's just underlining the fact that it's not a required property but as it's in definition it doesn't make much sense so... idk

[MilosPaunovic]

This seems like a good first issue, we just need to define what's expected behavior here @Ben8t.

[Ben8t]

Best to remove the null label if possible. If a property is optional, it can be null - no need for specific tag on this

[Mattjava]

Good evening. Me and a fellow programmer are willing to solve this issue. Please inform us of any steps we need to take to solve this issue other than setting up Kestra. Thank you.

[MilosPaunovic]

Hello @Mattjava,

You can tackle this issue, no problem! 🚀

What you need to do is to try and locate the section of the code responsible for this and find a way to remove the null label rendering.