Skip to content
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

cascade v-slot don't emit change of variables from scope #9438

Comments

@tcastelly
Copy link

tcastelly commented Feb 6, 2019

Version

2.6.2

Reproduction link

https://jsfiddle.net/cn09xg4k/

Steps to reproduce

There is a card component with userName and lastName. Each 200ms these variables are updated.
Between user and card components there is a wrapper, just to use a slot.

What is expected?

Variables in user component should be refreshed

What is actually happening?

These two variables are displayed only once and never updated


@tcastelly tcastelly changed the title cascade v-slot don't emit change on variable from scope cascade v-slot don't emit change of variables from scope Feb 6, 2019
@leopiccionia
Copy link

leopiccionia commented Feb 6, 2019

I'm not sure if the current spec allows putting the default slot inside <template/> (kind of treating it as a named slot), but it works without it: https://jsfiddle.net/leopiccionia/1097xjws/


Edit: it works just removing v-slot:default, too. https://jsfiddle.net/leopiccionia/myz3gte8/

@tcastelly
Copy link
Author

I'm curious to know if spec allows, in fact I can't remove the slot name from my wrapper because in my application I've some thing like header, footer.

https://jsfiddle.net/2d6fc4Lx/

@leopiccionia
Copy link

It seems to be a bug. Uncomment the fifth line (adding a default slot) and it works: https://jsfiddle.net/leopiccionia/bjr340vo/

@tcastelly
Copy link
Author

Correct ! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment