Show more context to where the error is

[jakeleventhal]

In the regular jest .toEqual(), you see the line in the JSON that is off with all the surrounding JSON lines. In this package's .toBeDeepCloseTo() you only see the line in the JSON that doesn't match - with no context of where in the JSON it appears - not even the key.

[maasencioh]

Thank you for your feedback, I'm updating this project in these days and I'll consider this

[jakeleventhal]

Is there any update on this? Another example of this as a pain point is if object keys dont match

I get the following logs

but if i use the native jest toEqual i get

clearly the latter is much better in terms of visibility

[jakeleventhal]

@maasencioh any update on this?