You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2020. It is now read-only.
Currently observer tries do a shallow comparison on next available properties. However if there is a data structure (object) passed into the props which is not an observable object, mobx-react assumes it might have been deeply mutated (similar to the assumption react makes) and re-renders to not take any changes.
Sometimes this is confusing for people, as they might expect shallow / pure comparison always. Should this be changed? Is it worth the potential risk of accidentally optimizing too much renders away?
Currently
observer
tries do a shallow comparison on next available properties. However if there is a data structure (object) passed into the props which is not an observable object, mobx-react assumes it might have been deeply mutated (similar to the assumption react makes) and re-renders to not take any changes.Sometimes this is confusing for people, as they might expect shallow / pure comparison always. Should this be changed? Is it worth the potential risk of accidentally optimizing too much renders away?
cc: @Strate @andykog @ConneXNL
The text was updated successfully, but these errors were encountered: