equal(value: T) type should be Loosely<T> when options ignore symbols or properties #172
Description
Support plan
- is this issue currently blocking your project? (yes/no): yes
- is this issue affecting a production system? (yes/no): no
Context
- module version with issue: latest
What are you trying to achieve or the steps to reproduce?
The equal() / equals() methods allow for an incomplete comparison by ignoring symbols or some keys. The types do not allow that. I am not sure if the type definition can make that distinctions but changing T to Loosely<T> should be sufficient and provide the same type safety without erroring on valid tests.