15. Form input bindings
Welcome to a binding discussion! Now that we know all about this superstar, v-model, which...
Read More18. Class bindings
Welcome to yet another binding discussion. Today, I will be schooling you on class bindings....
Read More14. Two-way data binding with v-model
Finally, the day has come, to understand the missing piece of the puzzle, data binding....
Read More12. Listening to keyboard and mouse events
Ready to listen for some key codes on your keyboard and some mouse buttons using Vue? Let’s dig deep then! Make sure you read up on “Listening to DOM events and Event modifiers” if you haven’t already. Because this is more of a continuation to what we already saw.
Read More13. Let’s use shorthands
Welcome back! Did someone say shorthands? Yes, that is what we will be focusing on today. We have been working with Vue directives for quite some time now. The v- prefix helps in more than one way. It visually represents that we are dealing with Vue related attributes in our code (the most important reason). By now you should have understood that v-bind and v-on are the two most frequently used directives in our templates. Why? Because we deal with events (especially click) and data binding all the time! So, for these two most often used directives, Vue gives us shorthands or a short way of writing them.
11. Listening to DOM events and Event modifiers
We have been kind of on a dry spell on the events front. Let’s learn how to listen to DOM events,click events in specific, today. Take a look at the starting code,
10. Rendering Lists Part 2 (Iterating over objects)
Hope you are already aware of iterating over array elements using v-for directive. In our applications, we deal with objects as much as arrays. So, without further ado let’s understand how to iterate over the various properties of an object. I hear you say, “what about an array of objects then?” I got you. We will handle that scenario too!
Read More9. Rendering Lists Part 1 (Iterating over arrays)
We deal with lists day in and day out. In our applications, we often face situations where we have to display arrays as lists whose items change dynamically. So, hardcoding array items in our HTML is not really an option. It is important that we know how to handle these dynamically changing arrays with Vue and not so surprisingly, we have another directive for just that! Tada, it’s v-for! As always, we will dive deep with loads of examples for clear understanding.
Read More8. Conditional rendering Part 2 (v-if and v-show)
Don’t we already have enough directives to handle conditional rendering? Do we still need v-show? One more thing to trouble our brains with? But what to do? Evan You (creator of Vue) added it for some reason while we were busy binge-watching Netflix. So, let’s see why this directive exists in the first place. Warning: This post is a continuation of “Conditional rendering Part 1” and hence I would recommend you to get a good hold of those concepts before proceeding any further. We discussed that v-if, v-else etc. can not only be applied to individual HTML elements but also to a block of elements using <div> or <template> etc. Let us first see an example with the <template> element and understand how it behaves as an invisible wrapper to the final result that is rendered to the DOM.
7. Conditional rendering Part 1 (v-if, v-else, v-else-if)
We don’t always want to render everything to our webpage. Based on a certain condition or the value of a particular expression, we might want to hide/show/attach or detach elements. This is nothing but conditional rendering – render elements based on a condition. This can be achieved using simple if-else statements. But, how are we going to do it with Vue? Let’s remedy that right here and right now! Vue directives come to our rescue one more time! We have v-if, v-else and v-else-if to help us in this regard. Let’s see one by one with examples, for a solid understanding. I will sprinkle a lot of visuals to ease the process.
