Programmatic Navigation

Programmatic Navigation: means we are possibly to navigate to a component by using $router instance rather than <router-link :to="#"></router-link>.

Example:

product.js route file
import Vue from 'vue'
import VueRouter from 'vue-router'

Vue.use(VueRouter)

const detail = {
template: `<div> product detail </div>`
}


const product = {
template:`<div>
productId:{{ $route.params.id }}
<router-view></router-view>
</div>`,
watch:{
'$route' (to, from){
console.log(from)
}
},
}
const routes = [
{ path: '/product/:id', name:'product', component: product,
children:[
{ path:'detail', name:'detail', component: detail }
]
}
]

const router = new VueRouter({
routes // short for `routes: routes`
})
export { router }

App.vue component file which contains goProduct method.
<template>
<div id="app">
<h2>Products</h2><br/>
<ul>
<li v-for="product in products" v-bind:key="product.id">
id:{{ product.id }}<br/>
name:{{ product.name }}<br/>
status:{{ product.status }}<br/>
<button @click="goProduct(product.id)"> Go to Product</button>
</li>
</ul>
<router-view></router-view>
</div>
</template>

<script>
import { router } from './routes/product';

export default {
name: 'app',
router,
components: {
},
data () {
return {
products:[
{id:1, name:'motobike', status:'old'},
{id:2, name:'fan', status:'new'},
{id:3, name:'watch', status:'new'},
{id:4, name:'glasses', status:'old'}
]
}
},
methods:{
goProduct( productId = null ) {
if(productId) {
this.$router.push({ path: `/product/${productId}/detail` })
}
}
}
}
</script>

When you click on Go to Product button, you see :
                                               productId:2
                                               product detail
that means it renders product and detail component as it was nested route.
Programmatic navigation is here 
this.$router.push({ path: `/product/${productId}/detail` })
You may see the each time you click on button the $router instance pushes path to get components rendered.
Navigation can be done with different syntax, more detail here: https://router.vuejs.org/guide/essentials/navigation.html

final result



Comments

Post a Comment

Popular posts from this blog

Vuex mapMutations

Image
VueX mapMutations: is used simply to replace this.$store.commit('abc') to   mapMutations(['abc','..']) . its functionalities are the same but mapMutations is more preferable and useful as it is able to combine different functions in mutations into one. Example: App.vue < template > < div id = "app" > < Counter /> </ div > </ template > < script > import { store , Counter } from './state/simple' export default { name: 'app' , store , components: { Counter }, data () { return { placeHolder: 'Focus on me' } }, } </ script > simple.js import Vue from 'vue' ; import Vuex , { mapGetters , mapMutations } from 'vuex' ; Vue . use ( Vuex ) const store = new Vuex . Store ({ state: { products: [ { id: 1 , name: 'pizza' , price: 10 }, ...
Read more

VueX Actions

Image
VueX Actions: can be used interchangeably with mutations however, actions  be used to commit mutations asynchronously whereas mutations can only be synchronous. Vuex Actions accepts context object as argument for each handler functions and this context contains commit, state, getters, and dispatch as it store instance. In order to call handler functions inside Actions properties from vue component, we use this.$store.dispatch('deductPrice').  When it dispatches from vue component, actions handler function will call mutations handler function with payload injected. Example: simple.js import Vue from 'vue' ; import Vuex , { mapGetters , mapMutations } from 'vuex' ; Vue . use ( Vuex ) const store = new Vuex . Store ({ state: { products: [ { id: 1 , name: 'pizza' , price: 10 }, { id: 2 , name: 'fan' , price: 20 }, { id: 3 , name: 'headset' , price: 30 }, { id: 4 , name: 'phone' , price: ...
Read more

VueX Modules

Image
VueX Modules: is important for large scale project as it make developer more easier to separate store state as module for example moduleOne and moduleTwo. Each module has its own state, getters, actions, mutations and namespace . However, namespace is optional. Nevertheless, it is best practice to have it to prevent some conflicts among modules state, actions, getters, mutations. Example: I have two modules with namespace inside. moduleOne const moduleOne = { namespaced: true , state: { products: [ { id: 1 , name: 'pizza' , price: 10 }, { id: 2 , name: 'fan' , price: 20 }, { id: 3 , name: 'headset' , price: 30 }, { id: 4 , name: 'phone' , price: 1004 } ] }, mutations: { deductPrice ( state ) { return state . products . map ( item => item . price -= 1 ) }, multPrice ( state , payload ) { return state . products . map ( item => i...
Read more