Adding a Watcher

Keep on Learning!

If you liked what you've learned so far, dive in!
Subscribe to get access to this tutorial plus
video, code and script downloads.

Start your All-Access Pass
Buy just this tutorial for $12.00

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Let's add a watcher! Create a new option called watch: {} set to an object of property names. For instance, since we want to run code when currentCategoryId changes, we'll add currentCategoryId set to the function that will be called. When Vue executes this, it will pass us two arguments: the new value of currentCategoryId and the old value. For now, just console.log(newVal, oldVal).

... lines 1 - 25
<script>
... lines 27 - 32
export default {
... lines 34 - 57
watch: {
currentCategoryId(newVal, oldVal) {
console.log(newVal, oldVal);
},
},
... lines 63 - 92
};
</script>

Let's see if this works! Move over to the browser: the console looks clear. Since we haven't actually added a way to change the currentCategoryId from within our app, head over to the Vue Dev Tools and change it there. I'll set it to 24, go back to the console and... yes! You can see the new value first and then the old value.

Load Products When currentCategoryId Changes

Back to catalog.vue! I'm actually going to delete these two arguments because I don't need them. Instead, our code can reference the new value directly via the currentCategoryId prop. Ok: when the currentCategoryId changes, we want to call this.loadProducts(). For the search term pass null for now.

... lines 1 - 57
watch: {
currentCategoryId() {
this.loadProducts(null);
},
},
... lines 63 - 95

This will trigger loadProducts()... which in turn will read the new currentCategoryId, get our products back from the server and update the products data. It's a fool-proof plan!

So let's check it out! I'll go back to the Vue Dev Tools, change the data to 23 and... ah! It works! With the loading screen and everything! I love that we can even change it to null and it goes to "All products". Awesome!

The only rough part is that if I, for example, search for "disk"... Actually let's try this under "office supplies". Search for "disk"... Then go find the <Products> component in the Vue Dev Tools and change the currentCategoryId to... let's say 24.

Ah! It returns everything! It did not apply the searchTerm on the products. The reason, of course, is that, in our watcher, we're passing this.loadProducts(null). Yep, we're saying:

Hey Vue! Load the products with no searchTerm".

And darn it, Vue is following our directions perfectly!

Suddenly we Do Want a searchTerm Data

If you look at data, we do not have searchTerm as a data key. Why? Because, until now, we didn't need it! All we needed to do - when onSearchProducts() was called - was use the term to immediately load the products. There was no need to store the search term anywhere for later. But now we do have a need! We do need to store the searchTerm so that when the currentCategoryId changes, we know what the searchTerm is.

Ok! Re-add searchTerm to data. And, down in onSearchProducts, say this.searchTerm = term. We can now remove the term argument from loadProducts and just say this.searchTerm instead.

... lines 1 - 32
export default {
... lines 34 - 50
data() {
return {
... lines 53 - 55
searchTerm: null,
};
},
... lines 59 - 66
methods: {
... lines 68 - 72
onSearchProducts({ term }) {
this.searchTerm = term;
this.loadProducts();
},
async loadProducts() {
... lines 79 - 81
try {
response = await fetchProducts(this.currentCategoryId, this.searchTerm);
... lines 84 - 85
} catch (e) {
... lines 87 - 89
}
... lines 91 - 92
},
},
};
... lines 96 - 97

That looks good! Now... let's see: up in created(), we don't need any arguments... and same in the currentCategoryId() watcher.

... lines 1 - 32
export default {
... lines 34 - 58
watch: {
currentCategoryId() {
this.loadProducts();
},
},
created() {
this.loadProducts();
},
... lines 67 - 94
};
... lines 96 - 97

Each will now automatically use the current search term. Let's try it!

Try it one more time!

I'll click on "Office Supplies" to get a full page refresh. Search for "disk"... and go over to the Vue Dev Tools one more time. Click on <Products>. change the currentCategoryId to 24 and... wow! No products found! If I change this back to null for "all categories"... it does find the product!

Of course, it's not updating the URL when we change the category... which it probably should. For that, we would need a Vue Router: a key component of single page apps - or even "mini" single-page "sections" that you might create on part of your site. With the Router, we could click on these links and have the URL change without a full page refresh. We'll save that topic for another time.

People! Friends! You made it through our first, gigantic Vue tutorial! Congrats! You deserve a snack... and probably some outside time.

There are more things to talk about - we'll save those for a future tutorial - but wow! You are already incredibly dangerous. I hope you enjoyed this process as much as I have! Vue is a very powerful, very fun tool to work with. So go build something awesome... then tell us about it!

And, as always, if you have any questions, comments or kitten videos, let us know down in the comments. All right, friends, seeya next time!

Leave a comment!

  • 2020-07-28 Matias Jose

    Hi Peter! I'm glad you liked our course! :) This course has a second part in the works and the Vue3 course is also in our plans! So there's a lot of Vue stuff in the future for you to get your hands on!

  • 2020-07-28 Peter Kosak

    Thank you Ryan and rest of the team for this course.

    It was a lot of new information for me, pretty much everything was new.

    Hope your new courses will use more and more Vue as a front end.

    I have learnt symfony back-end from your courses and now is a time to learn a front end from you where I am still struggling a bit.

    Cannot wait for Vue 3 course. Good job lads.