Skip to content

Any consideration to exposing createStubFromComponent for usage outside the library? #1175

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

Closed
scottadamsmith opened this issue Mar 9, 2019 · 1 comment

Comments

@scottadamsmith
Copy link

What problem does this feature solve?

I have some scenarios where I need (or want) to manually stub a vue component definition so that the definition coming from the import is already a stub. Would exporting this function be something that is worth considering? I think it would be incredibly useful. I also have some legacy tests that use Avoriaz for the time being and in those tests, I actually wrote an unfortunately complex function to build Vue mocks. Exposing this function would allow me to leverage this feature of vue-test-utils right away before I am able to fully transition all those tests to jest/vue-test-utils.

What does the proposed API look like?

I am guessing this is an oversimplification and there are some dependencies I am not seeing, but my hope is the effort is just to export this createStubFromComponent function from the library.

@ebisbe
Copy link
Collaborator

ebisbe commented Feb 15, 2023

#1564 (comment)

@ebisbe ebisbe closed this as completed Feb 15, 2023
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

3 participants