Hiya superstars! We have been locating elements for quite some days now. Let us switch gears and talk about “Assert and Verify” today.
To remember,The major difference between the two when the assert or verify condition/check fails is,
- Assert will fail the test and abort the execution of the current test case. All other test steps after that particular line of code are skipped
- Verify will log the failure but continue to execute the test case.
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 More
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-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.
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 More
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 More
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-else etc. can not only be applied to individual HTML elements but also to a block of elements using
<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.
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-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.
In our previous article, I gave you something to think about. Remember? Attribute binding! Time to take a deep look into it. As we all know, examples help us understand the concept in an easier way. So, what are we waiting for?
Imagine we have an anchor tag and we would like to bind a link to the
href attribute. Let’s try doing it using the text interpolation technique (template syntax) and check the result.