@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.

i was pointing at razvan’s answer, i know it’s for qapp.

@tof06 https://github.com/quasarframework/quasar/issues/7148#issuecomment-638768569

also native Intl.NumberFormat https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat

@JJ you can still post the forms, just don’t rely on native submit with names and what not, you will tie your formdata via model, and override the submit button, like i did in the example and let axios/fetch/whatever http client you use do the posting with your formData. updated the example to show you how to get the data https://codepen.io/metalsadman/pen/OJyoYPB. check your dev console.

also check the layout builder, your left menu seem to scroll along with the page, check the view prop config. https://quasar.dev/layout-builder

@JJ did you implement the test() method as well? since you need to traverse all thru the panels in order for them to be available. also check the QForm documentation https://quasar.dev/vue-components/form.

yeah, since it’s a child of q-page-container.

@dobbel core components are written in JS, i think for flexibility and performance (per Vue2), old version were used to be written in html. i only see pug used in some components of the docs, but most are in html format, and js render functions.

personally, i use html more since it feels more natural for me and render functions sometimes if i want to reuse it on several components as a mixin.

@user98034h use one of the header slots, taking the examples from here https://quasar.dev/vue-components/table#Header-slots. eg. https://codepen.io/metalsadman/pen/rNOXgRz.

@Cosby add content-class=“no-scroll”