Skip to main content

Usage of Vue Router

 The main feature of SPA single page is that a layer of front-end routing is added on the basis of the separation of front-end and back-end. That is, the front end maintains a set of routing rules. The user clicks the routing link on the page, which causes the Hash value in the URL address bar to change. The front-end routing monitors the change of the Hash address, and the front-end routing renders the component corresponding to the current Hash address to the browser. Vue-router is the routing solution officially given by Vue. It can only be used in conjunction with the vue project, and can easily manage the switching of components in the SPA project. For VueRouter, routing is the decision-making process of selecting a component for rendering based on a request path.

Install vue-router: nmp i vue-router

Write configuration items

import VueRoute from "vue-router"
import A from "../components/A.vue"
import B from "../components/B.vue"

export default new VueRoute({
    routes:[
        {
            path:"/a",
            component:A
        },
        {
            path:"/b",
            component:B
        }
    ]
})

Introduce registration

import Vue from 'vue';
import App from './App.vue';
//
import VueRouter from "vue-router"
import router from "./router/index.js"
Vue.config.productionTip = false;
Vue.use(VueRouter)
const vm=new Vue({
  render: h => h(App),
  router,
}).$mount('#app');

Specify placements

 <router-link></router-link>
<router-view></router-view>


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.