vuex

问题 Setting the "src" attribute of the html video element does not work with Vue.js and Vuex: <video id="myVideoEl" :src="myStreamSrc" autoplay="autoplay"> myStreamSrc is a computed value and is set in a mutation by an event handler: AddStream: function (state, plMyStream) { state.myRTCPeerConnection.addStream(plMyStream) state.myStreamSrc = plMyStream } When I run my application with that code, I get the following error: HTTP “Content-Type” of “text/html” is not supported. Load of media resource

问题 I have a Vue.js app. This app is using Vuex for state management. My store looks like this: const store = new Vuex.Store({ state: { items: [] }, mutations: { MUTATE_ITEMS: (state, items) => { state.items = items; } }, actions: { loadItems: (context, items) => { context.commit('MUTATE_ITEMS', items); } } }) ; In my Vue instance, I have the following method: loadItems() { let items = []; for (let I=0; I<10; I++) { items.push({ id:(I+1), name: 'Item #' + (I+1) }); } this.$store.dispatch(

问题 I have a login process where after sending a request to the server and getting a response, I do this: this.$auth.setToken(response.data.token); this.$store.dispatch("setLoggedUser", { username: this.form.username }); Now I'd like to emulate this behavior when testing with cypress, so i don't need to actually login each time I run a test. So I've created a command: Cypress.Commands.add("login", () => { cy .request({ method: "POST", url: "http://localhost:8081/api/v1/login", body: {}, headers:

问题 My first component (child component) like this : <template> ... </template> <script> export default { ... methods: { addPhoto() { const data = { id_product: this.idProduct} const item = this.idImage this.$store.dispatch('addImage', data) .then((response) => { this.$parent.$options.methods.createImage(item, response) }); }, } } </script> If the method addPhoto called, it will call ajax and then it will get response ajax I want to send response ajax and another parameter to method createImage.

问题 i am using the dragable and sortable with vuejs, and i have a issue, everytime i change the position of two divs for example, they change but the json array doesn't update. I am working with vuex, and i have in my component template this html: <draggable v-model="myList"> <div class="panel panel-primary" v-for="(value, key, index) in this.$store.getters.getDocumentAttributes"> <div class="panel-body quote"> <span @click="removeSection(index,key)" class="pull-right glyphicon glyphicon-remove

问题 I am building a Vue.js/Firebase authentication interface that includes an email verification component. So far, I have been able to successfully set up my interface so that the user is prevented from logging in until he/she clicks the verification link in the email sent to the inbox tied to the inputted address. I am noticing, however, that the email address still renders in the Firebase authentication portal, even BEFORE clicking the link in the verification email. This also seems to be the

问题 I am trying to bind the data on Kendo UI with the data from Vuex getters. I have tried the following but no luck. Please help whether where i am missing something on the vuex or on the kendo. Kendo Extensions: <kendo-grid :data-source="kendoDataSource"> </kendo-grid> Components: computed: { customers() { return this.$store.getters.customers; } }, data() { return { kendoDataSource: { schema: { data: function(response) { return response; }, model: { id: "CustomerID", fields: { CompanyName: {

问题 Please how may we delete items by key in a Vuex state object and still have computed properties bound to getters automatically update? I have a simple store: const state { users: {} // object of objects keyed by userid } const getters { admins: state => Object.values(state.users).filter(o => o.role === 'administrator'), managers: state => Object.values(state.users).filter(o => o.role === 'manager'), counters: state => Object.values(state.users).filter(o => o.role === 'counter'), } const

问题 When an object reference is passed to a Vue child component, and I want to update the value of one of the object's properties (using Vuex), the easiest way to do it is by passing the object reference and the new value to the mutation. The mutation then simply updates the property of the passed object. Is this legitimate? It seems bit too easy, and bordering on redundant (because I could do the reassignment in the component itself), except that the mutation can now be tracked. The alternative