feat: Add support for binding to nullable object

[svrooij]

🙋 Feature Request

If I have a FluentTextField it would be useful if it could be bound to an string? meaning that it might be not provided. Same for a FluentSelect, binding to a nullable object would mean there is no item selected.

🤔 Expected Behavior

Instead of forcing the binding value to be not nullable, if would be nice if it were to be ignored when bound to a nullable object and just show an empty state (placeholder)

😯 Current Behavior

You get a build error if you try to bind to a nullable object

💁 Possible Solution

🔦 Context

💻 Examples

[dvoituron]

This feature will be supported in the next major Release (v5).

[MarvinKlein1508]

This is connected to #2471