Is it good practice to v-bind: the route as a prop to the component?
If for instance that the view page is no longer on items/view/id (as its hard-coded on the component) or the <item-table> component is used in a directory not relevant to items/view there will be routing issues, is this acceptable practice? (From what Laracast Vue series I have seen, all of the axios routes are hardcoded)
Do you pass along many props like this ie: auth:user() or is there a better way to transfer blade directives that I'm missing?
Just feeling like a lot of the power of Blade is lost in exchange for the reactivity of vue.
Will have to see how route props align with workflow as I experience more of Vue but quite confident I will run into issues on larger projects with translations => trans() and nested components.