This also cleans up the way we are passing arguments around a bit by changing the signature of concreteAssert to also take the original callSpec as an argument. This reduces quite a bit of property duplication.

@jamestalmage Thanks! And sorry for late response.

Is there any place to be changed in README?

Yeah, needs some docs.

I am wondering if we shouldn't also just attach their entire original specification to the event, instead of copying over individual properties. That way they can attach arbitrary data specific to their own handlers

I am wondering if we shouldn't also just attach their entire original specification to the event, instead of copying over individual properties.

That's what you've done in this pull-req, right?

just attach their entire original specification to the event, instead of copying over individual properties. That way they can attach arbitrary data specific to their own handlers

Now I understand and it sounds good to me ;)

OK,
I've made all the changes and attached some documentation. We will need to document it better at some point, but I'd like to get this into use in AVA and make sure we like the API before spending a lot of time on that.

Thanks and agreed. If you have any changes not pushed yet, would you update this pull-req?

Sorry, I was working on a different branch and forgot.

@jamestalmage looks good to me. Thank you for the great contribution!

@jamestalmage Just released empower-core 0.3.0 🎉

I really appreciate your contributions.

Thanks @twada - I will write up an AVA PR using it in a few days. Thanks for working with us on making power-assert better for AVA.