Skip to content

test(v-stream): ensure the data gets passed correctly also on custom component #108

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

Merged
merged 3 commits into from
May 17, 2019

Conversation

briwa
Copy link
Contributor

@briwa briwa commented May 16, 2019

Hello. I saw a fix for #106, and I just thought that it could have been prevented by a test case so that similar problems won't happen again. What I did was just modifying the current test case for v-stream with data so that it also tests custom component instead of just a native element.

Also, just curious, why isn't the test using vue-test-utils? Is it because it's still in beta? I don't mind doing the refactor if it should be the way to go.

Let me know what you think. Thanks.

@regou
Copy link
Collaborator

regou commented May 16, 2019

why isn't the test using vue-test-utils? Is it because it's still in beta? I don't mind doing the refactor if it should be the way to go.

I don’t know why. And further PRs are welcomed!

@regou regou merged commit b610443 into vuejs:master May 17, 2019
@briwa briwa deleted the add-test-v-stream-custom-component branch May 17, 2019 02:26
@vue-bot
Copy link

vue-bot commented May 17, 2019

Hey @briwa, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants