@rubs here, also fixed some quirks when q-page-container is adding padding left same as q-splitter’s left width https://codepen.io/metalsadman/pen/YzPgKML

awesome, thx for your hardwork.

@karnjeet https://codepen.io/metalsadman/pen/ZgKexK

@patryckx check my sandbox currency formatter, you can replace the characters for ., prolly tweak the regular expression too. Its at src/components/base… https://codesandbox.io/s/0ybb3 sry cant check atm in mobile. mosuforge also has one using https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat

@jvmonjo can be achieved tho https://codepen.io/metalsadman/pen/YbXEjJ.

@jacklin10 be sure that you passed the store as an arg at your router/index.js’s export default function to access the store You don’t need to import your store.
Like I stated on my older reply in this thread https://forum.quasar-framework.org/topic/2825/store-is-no-longer-accessible-in-router/6… which is just above your post.
ie.

export default function({ store }) { // <<<<<<-- this is what you're looking for
  const Router = new VueRouter({
    scrollBehavior: () => ({ x: 0, y: 0 }),
    routes,
    mode: process.env.VUE_ROUTER_MODE,
    base: process.env.VUE_ROUTER_BASE
  })

  Router.beforeEach((to, from, next) => {
      ...
      console.log('LoggedIn: ', store.getters['auth/loggedIn'])
      ....
  })

  return Router
}

@lunne
call a method with your scoped props as a parameter in either save, show or hide events (hide event will not fire tho if you used buttons in your popup edit).
ie. @save="doSomething(props)", then you can process the prop object, you can either get the row prop in it which contains the __index property etc. or pass props.row if you just want the row object like so @save="doSomething(props.row)".

@PeterQF Its just a placeholder … means insert your code or whatever there, in this case an array of string paths ie paths : ['somepath']. https://github.com/robinvdvleuten/vuex-persistedstate/blob/master/README.md

@Rodrigo-Alves because it’s hard to maintain both.

you could’ve just un-commented the line.
export default function (/* { store, ssrContext } */) {
to
export default function ({ store }) {
also comment the line
import store from '../store'
since like doing it with quasar plugins, the store is also accessible in router/index.js.

@Kate use an object literal. ie.

...
  <q-badge :color="myTrClass(props.row.logLabel)">
     {{ props.row.logLabel }}
   </q-badge>
 ...

const color = col => ({
          'TRACE': 'grey-3',
          'WARNING': 'warning',
          'ERROR': 'red',
          'DEBUG': 'green',
          'INFO': 'purple'
        }[col])
...
myTrClass(logLabel) {
  return color(logLabel)
}

@keepingitsimple if it works like a vue plugin, install it via boot file https://quasar.dev/quasar-cli/cli-documentation/boot-files#Introduction.

these installation snippet would go into your boot file:

import Vue from 'vue';
import Croppa from 'vue-croppa';
// If your build tool supports css module
import 'vue-croppa/dist/vue-croppa.css';
Vue.use(Croppa);

@dhax Touchpan passes the event, so i think check that object and see which element it has current focus on, once it travels to other div you’ll do some checking if that element has selected class or not then add or remove the said class.

@JJ sry prolly = probably, anyway an example https://codepen.io/metalsadman/pen/OJyoYPB

Would be helpful if you provide a codepen. As for your handler you can use an arrow function to pass other params ie. v-touch-pan="evt => { setMove(evt, i, j) }". I guess you should check the examples in the docs, im guessing you need some modifiers also stopping other events like what you stated above. Gl

Wrap them in a parent qform or a form, prolly also need use keep-alive.

@turigeza it does require a bit of ninjutsu :), but i can select it.

Im able, but ofc not on the surface where there is no text.

Coz both have their uses, in wrapping you can fiddle with the template, which you cant using extend, unless you want to break it. In this case extend is appropriate since you are just changing the props.

I’d use whichever is appropriate, extend or wrapping.