Feature request: Rewrite some of the functionality of VueWrapper and align the vue API. about test-utils HOT 2 CLOSED

I wouldn't say we've got a specific position. The general development lifecycle for this library is just to assess and add things on a case by case basis, depending on what people want.

What I've seen historically is something like

1. User asks for feature to do X
2. Other users suggest alternative ways to do X
3. If the proposed solution is adequate, go with that
4. If it's not, discuss new / alternative / changes

In general, I think we want to avoid adding new features unless they solve a unique use case. If you think you have a use case for something like a exposeProxy, it might be worth sharing it before writing too much code.

In my opinion tampering with the component isn't good, it's better to just interact like a user does (click, etc) but happy to discuss more! Have you got a specific class of tests you are struggling to write without proxy access?

from test-utils.

@jason-chang We can already access everything that is exposed (and not exposed) by the component on the VM, so I don't think we need to add another property.

If you have a specific use case that can't be done currently, feel free to ping us with a repro and we'll gladly reopen and discuss!

from test-utils.