-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Global Stringify #68
Comments
@felangel could you elaborate on the behavior of the "default" (normal) setting? |
@zepfietje the normal setting will result in just the runtimeType being printed. |
@felangel what's the difference between |
Normal will defer to the EquatableConfig setting never will never stringify. |
So why exactly would we need an |
@zepfietje good call...I've updated the issue to maintain a bool (which makes this a non-breaking change). The PR is open at #69 👍 |
@felangel this issue can now be unpinned. 👍 |
Is your feature request related to a problem? Please describe.
It would be nice to have a way to globally configure
stringify
for allEquatable
instances. The proposal includes a breaking change to refactorstringify
from abool
to anenum
in order to be able to support a "default" (normal) setting in addition to an "enabled" (always) and "disabled" (never) setting.Describe the solution you'd like
If
stringify
is overridden for an individualEquatable
it will take precedence over theEquatableConfig
value.Addresses #60 and #65
The text was updated successfully, but these errors were encountered: