Skip to content

v-template with custom components throws an exception #107

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
rigor789 opened this issue Jan 15, 2018 · 1 comment
Closed

v-template with custom components throws an exception #107

rigor789 opened this issue Jan 15, 2018 · 1 comment
Labels

Comments

@rigor789
Copy link
Member

Reproduction:
https://play.nativescript.org/?template=play-vue&id=2zz4p6

@rigor789 rigor789 added the bug label Jan 15, 2018
@rigor789
Copy link
Member Author

Leaving slack log here about the issue just for reference:


rigor789 [3 minutes ago]
for now you can stick the templates inside the v-template tags, and extract them to a component when it's fixed

rigor789 [2 minutes ago]
briefly the issue is that for list-views I have to create empty views for nativescript, at which point I don't have access to the data that will be show in that particular view

rigor789 [2 minutes ago]
and it's solved using a deep proxy object which returns a proxy for up to 10 levels deep (edited)

rigor789 [1 minute ago]
a.b.c.d.e.foo.bar will be a proxy

rigor789 [1 minute ago]
so the compiler doesn't complain about trying to read b of undefined

rigor789 [< 1 minute ago]
and I'm guessing there is a slight difference how the components are converted to render functions, and it causes the issue

@nativescript-vue nativescript-vue locked as resolved and limited conversation to collaborators May 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

1 participant