-
Couldn't load subscription status.
- Fork 113
feat: fireEvent.emit #234
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
feat: fireEvent.emit #234
Conversation
Hi! Thank you for the initiative here.
I think this is already solvable by clicking the button and using emitted() to inspect the result. With this addition, tests would rely on implementation details (the custom event) instead of interacting with the component as a user would.
Hi! Thank you for the initiative here.
I think this is already solvable by clicking the button and using
emitted()to inspect the result. With this addition, tests would rely on implementation details (the custom event) instead of interacting with the component as a user would.
I see, what you mean. I'll try to follow this way and return back, if something goes wrong or I'll have example to continue the discussion.
Hello!
I've already asked for help with custom vue events emitting in #233, but I think, it would be nice to have unified way to fire both
DOMandvueevents.I propose to use
fireEvent.emitas syntax sugar over the__vue__.$emitmethod.