Dmitriy Lazarev

But why do we need to be able to remote it?

I mean that you said `Also, I think we'll need to be able to remove a wrapper too right?` Why do we need to remote it?

Oh, sorry. I didn't notice, that I did a typo :)

@jnicklas @cowboyd I have an idea how we can bypass the first two limitations. When we get interaction in our wrapper we calculate hash from interaction name, available filters/actions, default...

Yeah, I already thought about that. But actually for the playwright we can have another solution. We can add function `exposer`, ask user to put all his interactors there. That...

@cowboyd, yeah, we missed that point

Yeah, we can move non-printable keys set out to the keyboard package

Most interactors override the locator method. So I think we should implement trimming on the internal level, like adding the special `trim` matcher.

@dagda1 Sorry, I just created an example app by using backstage create app wizard. Should I copy-paste to-do list from the issue?

We can add a special enum for that. But it requires to do a few of changes to matchers and output formaters