Asymmetric matches should be formatted

[just-boris]

What is the current behavior?

Jasmine gives you special values that you can use at the right side of toEqual, to make the comparison more flexible. After #2213 this also will be landed as a part of Jest API.
However, there is a problem with error message formatting. Given the following assertion:

expect({
  a: 1,
  b: {
    test: false
  }
}).toEqual({
  a: 1,
  b: jasmine.objectContaining({
    test: true
  })
})

Produces the following error message:

Expected value to equal:
      {"a": 1, "b": {"sample": {"test": true}}}
    Received:
      {"a": 1, "b": {"test": false}}

What is the expected behavior?

I expect to have printed special format for asymmetric comparison value.
For example, pure Jasmine detects special value and formats it accordingly:

Expected 
  Object({ a: 1, b: Object({ test: false }) }) 
to equal 
   Object({ a: 1, b: <jasmine.objectContaining(Object({ test: true }))> }).

It would be nice to do this in Jest as well. It also worth to mention that all asymmetric values have a special method .jasmineToString that gives pretty-printed value for message.

[thymikee]

We're actively working on this here: #2397. Feel free to join the discussion. Closing the issue.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.