What are the issues you’re running into with vue-router? I’m currently trying to set up testing similar to what is generated by the vue-cli webpack template but am struggling…

I worked around this by adding $drawer-screen-width-threshold = 9000px in themes/app.mat.styl

The drawer will always be hidden and the button to toggle it will always be visible (on resolutions lower than 9000px wide)

I recently tried to pass an array from Vuex state into a q-select component of type ‘toggle’ and noticed that the select-component modifies the array in place without emitting events. This obviously breaks the Vuex pattern and prevents me from doing this:

skills: {
  get () {
    return this.$store.getters['ALL_SKILLS']
  },
  set (values) {
    this.$store.commit('SET_SKILLS', values)
  }
}

To work around this I created a local array in the component itself and then watch that array for changes. If there’s a change, I call the Vuex mutation. This solution works, but is there a way I can get the above code to work with q-select of type ‘toggle’?

I recently tried to pass an array from Vuex state into a q-select component of type ‘toggle’ and noticed that the select-component modifies the array in place without emitting events. This obviously breaks the Vuex pattern and prevents me from doing this:

skills: {
  get () {
    return this.$store.getters['ALL_SKILLS']
  },
  set (values) {
    this.$store.commit('SET_SKILLS', values)
  }
}

To work around this I created a local array in the component itself and then watch that array for changes. If there’s a change, I call the Vuex mutation. This solution works, but is there a way I can get the above code to work with q-select of type ‘toggle’?

I use Selenium to do E2E tests of a project built using Quasar but I’m running into dead ends when trying to assign IDs to various HTML elements so I can access these elements directly in my tests.

It’s obviously easy to assign custom IDs to components I’ve written myself, but anytime I use a Quasar component which in turns generates a bunch of HTML elements (often with child elements of their own) I have no way of assigning IDs to these elements and so I can’t access them directly in my tests.

Am I going about this the wrong way? Is there a better option for E2E testing? Or is the only option to look at the generated HTML code and dig down into child elements manually in the tests?

I worked around this by adding $drawer-screen-width-threshold = 9000px in themes/app.mat.styl

The drawer will always be hidden and the button to toggle it will always be visible (on resolutions lower than 9000px wide)

What are the issues you’re running into with vue-router? I’m currently trying to set up testing similar to what is generated by the vue-cli webpack template but am struggling…

@rstoenescu I ended up going that route! Thanks!

I’m trying to update the ‘message’ property of a progress Dialog while it is showing. The progress bar updates when the given progress variable changes but I cannot get the message to update.

I’m updating the progress percentage with data returned from an API call. That same data contains a progress stage string and this is what I want to show in the dialog.

Any suggestions?