Actually, if your CommonModule is included in SharedModule, you don’t need to import CommonModule where you’re already importing SharedModule.
The best practice would be to only import CommonModule in SharedModule. And use SharedModule along the App.
hey! Sure! Wrap one in the other.
If you need a condition that determines if you loop, then, wrap your
v-for inside a
And, if you need a condition for each element of an array, then put the
v-if on each child of the
// Loop if condition is met <div…
About comments, I personally dislike comments, I try to avoid them as much as…
The thing is that
reduce, for example, also exists in ES2015. Compilers like babel, for example, compile ES6 into ES2015. And the result is still a reduce function.
The performance issue is in the under the hood implementation of
const add = (a, b) => a +…
Thanks a lot for the feedback!
I found that adding the mixin name was creating more confusion than readability. But it also depends on the mixin, the situation and the developer.
By adding a simple $_, like in $_updateUser, I found that the code was way more readable, and could differentiate between…
Hey! Makes sense. To be honest, I also prefer to have both in camelCase, for global finding a prop, for example.
VueJs team strongly recommends to use kebab-case in template, but is not critical.
It makes sense to use camelCase in JS and kebab-case in HTML, but it also makes…