Skip to content
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

Improve stringification of captor.capture() matcher #269

Open
searls opened this issue Jun 24, 2017 · 0 comments
Open

Improve stringification of captor.capture() matcher #269

searls opened this issue Jun 24, 2017 · 0 comments

Comments

@searls
Copy link
Member

searls commented Jun 24, 2017

right now, captor.capture() matchers are printed out with an ugly toString() in error messages. they should be niceified like the other matchers.

currently just got:

All calls of the test double, in order were:
  - called with `("target", undefined, function (name, originalValue) { 
      return (0, _chainPrototype2.default)(overwriteChild(originalValue, '.' + name), name, originalValue, original); 
    })`.                                                                                    

That whole third arg should have been captor.capture() or the like

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant