Skip to main content

Two lifecycle hook functions activated and deactivated in Vue routing

 The creation and mounting of components that use the cache <keep-alive> at the beginning will be executed the same as the components that do not use the cache, but the components that use the cache will not be destroyed when switching components, and the activated function will be triggered when switching back again. , the deactivated function will be triggered when switching, and components that do not use the cache cannot use the activated function. Simply put, the activated function is a hook function after the page is activated, which is triggered as soon as the page is entered. So when we use component caching, if we want to send a request every time we switch, we need to write the request function in activated, and in created or mounted, it will only work when the component is loaded for the first time.

Here are the usage details:

<keep-alive :include="['DDD']">
          <router-view></router-view>
        </keep-alive>
//
activated() {
    console.log("hello")
  },
  deactivated() {
    console.log("OvER!!!")
  },

Comments

Popular posts from this blog

favicon.ico 404 Not Found Causes and Solutions

 What is favicon? It is the abbreviation of Favorites Icon. Its function is that in addition to displaying the corresponding title in the browser's favorites, icons can also be used to distinguish different websites. When I encounter this kind of error, I feel very uncomfortable. There is obviously no problem. Why is a 404 error reported? The following is the solution.

Use of custom events in Vue components.

 The parent component uses props to pass data (such as a method) to the child component, and the child component needs to use custom events to pass data back to the parent component! We can use v-on to bind custom events, and then pass them to subcomponents, which will call after receiving the method. Each Vue instance implements the Events interface, that is: use $on(eventName) to listen for events and $emit(eventName) to trigger events.

mapState, mapGetters, mapMutations, mapActions in vuex

 The above four objects are all in the vuex plug-in store, which is often used to store some data shared globally. But I still feel a little uncomfortable when using it, that is, I wrote a lot of repeated prefixes. At this time, these four objects appeared, which solved this pain point very well. mapState is mainly used to manipulate and obtain data, mapGetters is equivalent to computed properties, and mapMutations and mapActions are simplifications of mutation and action. They can be written as both objects and arrays.