If you’re going to v-model a computed, it needs a setter. Whatever you want it to do with the updated value (probably write it to the $store, considering that’s what your getter pulls it from) you do in the setter. If writing it back to the store happens via form submission, you don’t want to … Read more
According to this awesome tip from Vuedose blog Vue.js 2.6 introduced some new features, and one I really like is the new global observable API. Now you can create reactive objects outside the Vue.js components scope. And, when you use them in the components, it will trigger render updates appropriately. In that way, you can … Read more
To answer this for any particular case, one would need the launch.json configuration being used, and the source folder structure, at minimum. I have a true story from just last week to illustrate why: Background I recently inherited a relatively small Vue project, and immediately encountered the same problem. Breakpoints in VSCode were “jumpy” in … Read more
In Addition to the accepted answer I wanna provide you with a workarround for the getter which is missing in the answer. Debug the Store In any case you can call console.log(this.$store) to debug the Store. If you do so you will see the getters are prefixed with the namespace in their name. Access namespaced … Read more
import router from ‘./router’ and use router.push Simple like that.
I suppose getDetailMenu is calling API method to get listMenu. You can create route dynamically using addRoutes method Pseudo code created() { this.getDetailMenu(this.$route.path) .then((listMenu) => { // you need to return listMenu from getDetailMenu listMenu.forEach((item, index) => createAndAppendRoute(item, index)) }) }, methods: { createAndAppendRoute: (item, index) => { console.log(item, index) // Base on your data, … Read more
Question 1: Why did the Vuejs developers decide to do it this way? Answer: When your application becomes large, and when there are multiple developers working on this project, you will find that “state management” (especially the “global state”) becomes increasingly more complicated. The Vuex way (just like Redux in react.js) offers a new mechanism … Read more
Alright, so the behavior is totally logic. Vuex is not supposed to be persistent. For any persistence on the front-end, you need either: cookies localStorage pass it in the URL (query params) IndexedDB get the data back from making a call to a backend Some of the packages here may be useful: https://github.com/vuejs/awesome-vue#persistence If you … Read more
In my child component, there are no buttons to emit changed data. It’s a form with somewhat 5~10 inputs. the data will be submitted once you click the process button in another component. so, I can’t emit every property when it’s changing. So, what I did, In my parent component, I can access child’s data … Read more
As suggested here, what you can do is to export your store from the file it is in and import it in the routes.js. It will be something like following: You have one store.js: import Vuex from ‘vuex’ //init store const store = new Vuex.Store({ state: { globalError: ”, user: { authenticated: false } }, … Read more