Closed lulupointu closed 2 years ago
Hi @lulupointu š Thanks for opening an issue and sorry for the delayed response!
I'd prefer to avoid making this change because, as you mentioned, Object
is the preferred usage.
Closing for now but feel free to comment if you feel strongly about this change and I'm happy to continue the conversation, thanks! š
Is your feature request related to a problem? Please describe. When trying to mock certain object, their
==
override might usedynamic other
instead ofObject other
, this will make mocking impossible becauseMock.==
usesObject
.An example of this is the
Hive
package, here is an example:The compiler will complain:
Describe the solution you'd like Change
To:
Describe alternatives you've considered Opening an issue into the other package, since
Object
is the right think to use. Which I didAdditional context Once again I know using
Object
is the right thing to do. However sinceMock
sub-classes will never be sub-classed using the widest possible element (dynamic
) might be better. I would understand if you don't want to though, I just wanted to let you know this could be an issue for some.Also thanks so much for this package and the other you created (read bloc). I've been using your packages since I started flutter and they helped me to learn a lot. So thank you !