Skip to content

Nullable properties won't fire a change if you set the value to null from unitialized state #555

@Temp1ar

Description

@Temp1ar

Don't know if it is by design, but I was quite surprised to discover this. I have a property with nullable int. I'm doing AdviseOnce on the backend and set the same property to null on the frontend, expecting advise to trigger, but it doesn't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions