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
Hi, there might be cases where you want to customize the behavior a bit more and it would be useful to be able to decide which props to use.
From what I see EquatableMixin will be removed, so there is no way to do it currently in version 3.0.
Thanks
By the way, there are packages that depend on Equatable and without the Mixin, in case you don't use all the props but only a few like my case now, you will be forced to do it manually when version 3.0 comes out.
There, couldn't the mixin also be preserved apart from the new macro?
The text was updated successfully, but these errors were encountered:
MiniSuperDev
changed the title
Add option to exclude or select props with the new
Add option to exclude or select props with the new Equatable macro
Dec 26, 2024
Can you please provide some context/use cases to illustrate why you only want to include certain properties in the value comparison? That seems like a misuse of package:equatable and you'd be better off writing your own operator== override.
Hi, there might be cases where you want to customize the behavior a bit more and it would be useful to be able to decide which props to use.
From what I see EquatableMixin will be removed, so there is no way to do it currently in version 3.0.
Thanks
By the way, there are packages that depend on Equatable and without the Mixin, in case you don't use all the props but only a few like my case now, you will be forced to do it manually when version 3.0 comes out.
There, couldn't the mixin also be preserved apart from the new macro?
The text was updated successfully, but these errors were encountered: