Just adding a question mark ? will make it optional. { path: ‘/offers/:member?’, … }, It works for Vue Router 2.0 onward. Source: https://github.com/vuejs/vue-router/issues/235#issuecomment-245447122
After some experimenting with vue-cli3, i found that you can use vue add to setup components you missed. Use vue add router That set up the routing and created some sample components Home and About. This also work for other modules like adding vuetify with vue add vuetify. You can read more about vue add … Read more
The syntax for the “apollo” options you listed do indeed look correct- assuming you’re intending to use the package “vue-apollo” to work with Apollo. If you’re getting this error it may mean that “vue-apollo” hasn’t been installed, or there’s some problem with the installation. If you look in the Vue Chrome debugger tool on one … Read more
I had the same exact issue, and kept looking for days, till I stumbled upon this github post: https://github.com/storybookjs/storybook/issues/12006 Currently in my React (am sure vue approach will be similar), I do following: import React from ‘react’; import CheckboxGroupElement from ‘../CheckboxGroup’; import { STORYBOOK_CATEGORIES } from ‘elements/storybook.categories’; import { useArgs } from ‘@storybook/preview-api’; export default … Read more
Vuex is perfectly compatible with typescript using these vuex imports: import {GetterTree, MutationTree, ActionTree} from “vuex” The example below shows the easiest and most complete way to use vuex in typescript. Principal store file: import Vue from ‘vue’ import Vuex from ‘vuex’ import { GetterTree, MutationTree, ActionTree } from “vuex” import MySubModule from ‘@/store/submodule’ Vue.use(Vuex) … Read more
Array change detection is a bit tricky in Vue. Most of the in place array methods are working as expected (i.e. doing a splice in your $data.names array would work), but assigining values directly (i.e. $data.names[0] = ‘Joe’) would not update the reactively rendered components. Depending on how you process the server side results you … Read more
The type is just Event. Relevant information is on e.target property.
One possible answer that I just found thanks to a GitHub issue is the following. It is possible to use the key attribute that is also used for v-for to let Vue track changes in the view. For that to work, you have to add the attribute to the router-view element: <router-view :key=”$route.fullPath”></router-view> After you … Read more
I think in your case you are looking for a solution like this example: uploading a image and previewing it before submission <template> <div> <img src:”previewImage” class=”uploading-image” /> <input type=”file” accept=”image/jpeg” @change=uploadImage> </div> </template> <script> export default { name:’imageUpload’, data(){ return{ previewImage:null } }, methods:{ uploadImage(e){ const image = e.target.files[0]; const reader = new FileReader(); … Read more
My solution was very simple (see v-model=”tags[index]”): Instead of doing this: <template v-for=”tag in tags”> <TagView :key=”tag.key” v-model=”tag” /> </template> You should do this: <template v-for=”(tag, index) in tags”> <TagView :key=”tag.key” v-model=”tags[index]” /> </template> The reason is you cannot pass iterated object tag into v-model for modifications. Please find more info about this: Iterating a … Read more