Recursively find parent for callbacks about vuetable-2 HOT 2 OPEN

@stevendesu Thanks for you suggestions and contributions later. (Yeah, I've noticed) :) Even though, I do not have time to follow up on them at the moment, but I did read and really appreciate it.

When I first implemented this, I had a mixed feeling about it. Trying to contain everything within the component itself and exposes its functionalities to the externals via api and events.

As in using jquery, I see this as a convenient feature to automatically look up its parent for override-able function, but I'm trying not to go beyond its immediate parent as I usually don't have a need for that. And I really don't know if there will be any case that requires going up the chain or not. Because if uses incorrectly, it will be very hard to find the problem.

What's your opinion on this?

from vuetable-2.

Thinking about it for some time, I feel like the proper solution is instead of passing the name of the callback, the actual callback should be passed in. This way the component is handed everything it needs to operate and does not need to go looking for it in the parent.

Looking at the code, this is actually how it's written -- if a function is passed instead of a name, the function is executed. I might update the tutorial, however, to make it clear that this is possible (and also the preferred method, as it would be more performant)

https://github.com/ratiw/vuetable-2-tutorial/blob/master/doc/lesson-06.md

Currently the tutorial only demonstrates passing a string for the callback

from vuetable-2.