uno-mvux-records

MVUX list flicker and mis-identification occur when immutable records lack correct key equality. Enforcing IKeyEquatable ensures stable list rendering by precisely tracking item identity across updates.

Configure key equality by defining partial records with an Id or Key property to auto-generate IKeyEquatable, or apply explicit [Key] attributes to specify custom or composite key properties for MVUX data models.

Yes, you can use composite keys or custom property names by applying explicit [Key] attributes. This overrides default Id or Key discovery to ensure precise entity matching in MVUX messaging and state scenarios.

No, manual implementation is unnecessary. The system auto-generates IKeyEquatable for partial records containing an Id or Key property, and supports assembly-level defaults to configure key property discovery across MVUX models.

Update immutable MVUX records using with-expressions to create modified copies. This preserves key equality and IKeyEquatable implementation, ensuring the updated item maintains stable identity within UI list rendering.

Assembly-level defaults configure key property discovery and safe defaults for MVUX models, but require partial records with recognizable Id or Key properties, or explicit [Key] attributes, to correctly enforce immutable record key equality.