Soroosh Taefi

Hi @Yue-plus, thanks for reporting this issue. Could you please provide more info about which version of Hilla caused this issue for you?

@grimsi Thanks for creating this issue. To my understanding, proper handling of optional parameters wasn't in the scope of supporting Kotlin's native nullability from the beginning, but I agree that...

Debugged this a bit, and realized that with a class like this: ``` class User( @field:JsonProperty("email_addresses") val emailAddresses: Set ) ``` in the `resolve` method of `KotlinNullabilityPlugin`, while traversing the...

Anyway, ignoring the underlying reason for getting a `CompositeTypeSignatureNode` for this sample property, the code can change so that no more ClassCastException happens at runtime. But, regardless of the node...

> if we don't find a member property named email_addresses we look for a member property marked with @JsonProperty("email_addresses") Not that I'm against this suggestion, but to me, this sounds...

According to internal discussion, this will be put on hold (or may be closed), until the latency compensation could be implemented based on the local stack of pending changes and...

@ZheSun88 seems we don't need this anymore, correct?

There could be a small problem that needs investigation: The fix we merged last week might still not work for a specific case: If a ListSignal is conditionally rendered, e.g....

We can close this as duplicate.

It seems to work as intended, explained here: https://vaadin.com/forum/t/form-binding-firstnamecomponent-example-renders-undefined-as-input-value/166913/4