Initializing vue tables drives me crazy about vue-tables HOT 4 CLOSED

Why are you passing props to a non-component? It seems like your columns prop interferes with the columns array that you are returning.
Also, you need to pass a url prop to the server component.

from vue-tables.

sorry @matfish2 , I removed that because I saw no relevance in it. You are right all of thm should be in there and they are in my code.

It's the loading in webpack that's failing and I don't know why or how to reproduce it, just thought that this footprint would suffice if you encountered the problem yourself.

I also tried the basic examples from the Readme file all of them had an issue in the "created" function, with the "options" property.

Thank you for responding so quick.
Do you think you need some more details on this ?

webpack loaders are vue and vue-html

from vue-tables.

I didn't encounter it myself because I am using browserify. So you'll have to figure that one out yourself.

The last error you included - which is the one I was referring to - is not a compiler error, but rather a run-time one. It suggests that your columns prop is undefined.

from vue-tables.

Alright so the problem was is the first piece of code I submitted, not sure why it happened, but this is my understanding:

if I defined the prop "columns" without a default it would throw that error, also it would not call the "data" function while having the props defined.

Solution 1: I removed the whole "props" entry from my component definition and it worked.
Solution 2: I moved the logic from "data" to "props" defaults and it worked.

Which one would be recommended ?

from vue-tables.