vue implements forward refresh effect

This time I will bring you vue to achieve the forward refresh effect. What are the precautions for vue to achieve the forward refresh effect? ​​The following is a practical case, let's take a look.

Recently I am trying to do mobile projects using vue. I hope to achieve the effect of forward refresh and backward non-refresh. That is, the loaded interface can be cached (no need to reload when returning), and the closed interface can be destroyed (reloaded when re-entering). For example, a->b->c moves forward (b, c) and refreshes, and c->b->a moves backward (b, a) without refreshing.

Because

keep-alive will cache all loaded interfaces, it is impossible to destroy the interface when returning, resulting in the interface not being reloaded when re-entering. So the first solution that comes to mind is to call this.$destroy(true) to destroy the interface when clicking the return button on the interface. However, there will be a physical return key on the mobile android device. If you return through the physical return key, it cannot be processed. Although the return event of Android can be rewritten to call the js method, the global method of js is called, and the interface on the top layer cannot be specifically destroyed.

So we need to find another way. Fortunately, this article inspired me to keep-alive of vue-router. Thank you to the author for sharing.

It would be nice if I could know whether

routing is going forward or backward. In this case, I can set the keepAlive of the from route to false and the keepAlive of the to route to true when going backward. You can reload the route whose keepAlive was set to false before moving forward again.

No more nonsense, there are three interfaces simulated here, login to server to main.

First of all, I set a strict hierarchical relationship for the paths of these three interface routes, and set keepAlive to be true, which requires caching by default.

const router = new Router({
 routes: [
  {
   path: '/',
   redirect: '/login'
  },
  {
   path: '/login',
   component: Login,
   meta: {
    keepAlive: true
   }
  },
  {
   path: '/login/server',
   component: ServerList,
   meta: {
    keepAlive: true
   }
  },
  {
   path: '/login/server/main',
   component: Main,
   meta: {
    keepAlive: true
   }
  }
 ]
})

Since the paths of these three interfaces are at different levels, I can use the beforeEach hook to determine when to go back. When going back, set the keepAlive of the from route to false and the keepAlive of the to route to true.

router.beforeEach((to, from, next) => {
 const toDepth = to.path.split('/').length
 const fromDepth = from.path.split('/').length
 if (toDepth < fromDepth) {
  console.log(&#39;后退。。。&#39;)
  from.meta.keepAlive = false
  to.meta.keepAlive = true
 }
 next()
})

Finally, wrap the interface that needs to be cached with

keep-alive , so that the effect of refreshing when going forward and not refreshing when going back can be achieved.

<keep-alive>
     <router-view v-if="$route.meta.keepAlive">
      <!-- 这里是会被缓存的视图组件 -->
     </router-view>
    </keep-alive>
    <router-view v-if="!$route.meta.keepAlive">
     <!-- 这里是不被缓存的视图组件 -->
    </router-view>

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!

Recommended reading:

Summary of jQuery code optimization methods

How to deal with incomplete page display in 360 browser compatibility mode

box-reflect to achieve reflection effect

The above is the detailed content of vue implements forward refresh effect. For more information, please follow other related articles on the PHP Chinese website!