don't do anything If a state is "updated", but it hasn't actually changed about litho

[vinc3m1]

Is this an upcoming fix? or permanently backlogged now?

[appleguy]

@mihaelao is this behavior now implemented by default? Alternatively, is there a specific API that a client needs to use in order to ensure that equivalent states don't trigger an update? cc @vinc3m1

[mihaelao]

Sorry for the delay, I missed this! We didn't invest time in this because it's not a common problem, you can avoid this situation by checking the state value before triggering an update. Are you facing an issue with this?

[mihaelao]

Closing this as we've decided not to invest time in this; comparing two state objects transparently on the framework is not trivial, as we could be dealing with complex objects, and asking the developer to implement a comparison method when using state API is unnecessary overhead. This can already be handled with the current API by conditionally triggering state updates.