News for hackers. Stuff that matters.
Re:VueJS cheat sheet by wjossey on Monday October 29, 2018 @02:08PM (#18329682)
I put all the code in a single gist to make it easier to reason. This example (b/c it's basic) looks like more-code that's just generally unnecessary. In practice though, I've found those-sub components, even when it's just a button, tend to benefit from splitting out. You end up doing some styling to them, having them inherit from a parent button component, etc.

https://gist.github.com/wjossey/0d7ca1a3c2040e1c376a914941b8...

Re:VueJS cheat sheet by mimischi on Tuesday October 30, 2018 @03:33AM (#18334515)
Thanks, I haven't realized I could pass a method to a child, which acts on the context of the parent (that's what's happening here, right?).
Re:VueJS cheat sheet by wjossey on Tuesday October 30, 2018 @10:54AM (#18337034)
What I showed you is just a callback chain. Vue recommends all changes flow UP. So, you can imagine a button is a leaf node that when pressed calls a function passed to it. That function belongs to the parent component in this case.

If you ever did traditiona JavaScript programming earlier in this century, you’ll be familiar with this pattern which is referred to as “callback hell” by some.

If you ever go to use a third party library like Vuetify, the components you use in essence follow the same pattern.