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

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

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

@venkyvb
Try something like this.

 <q-table
    :data="tableData"
    :columns="columns"
    row-key="name"
    :rows-per-page-options="[0]" 
    :pagination.sync="pagination"
    hide-header
    hide-bottom
  />

data () {
  return {
    pagination: {
         page: 1,    
         rowsPerPage: 0 // 0 means all rows    
     }
}

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

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

@manubi I would say, via making a new quasar CLI project and port your code, follow the docs everything about quasar CLI, boot filea, quasar.conf.js file which is similar to your vue.conf.js and etc… About quasar v2 using Vue 3, it’s still in the works. https://forum.quasar-framework.org/topic/6960/quasar-with-vue-3

@weide you probably need to upgrade your @quasar/app package too https://quasar.dev/quasar-cli/app-upgrade-guide.

@ghada yes, see the code of this example https://quasar.dev/layout/grid/flexbox-patterns#Example--Masonry-like-table-grid

@murrah I use a recursive function for this, my node structure is unlimited nesting. i use scope-slots ie.

// node model
[{
  id: 1, // unique id
  name: '',
  description: '',
  children: [], // same array of objects like this node
  parent_id: null, // null indicates this node is root, else holds id of its immediate parent
  ... // other props
}]

getRootNode (tree, node) {
      let curNode = node.parent_id !== null ? tree.getNodeByKey(node.parent_id) : node
      if (curNode.parent_id !== null) {
        curNode = this.getRootNode(tree, curNode)
      }
      return curNode
    }

@mfrz6 use Promises https://codepen.io/metalsadman/pen/LYZZyGy?editors=1010

@haizad v-for="data in props.row.data" … :label="data.name", you can simply display the value of props to see what the structure is and would’ve avoided making guesses like you are doing now. Ie. {{props}}, or see API card scope slot section what objects exposed in the scope.

@Sacrekin done, though I just linked the GitHub ticket, as the timetables are up to the core guys. It’s better the discussion to be there IMHO, for tracking.

https://github.com/quasarframework/quasar/issues/7836

https://quasar.dev/start/roadmap

@Q-Brad this article discusses about that https://www.binarcode.com/blog/tips-for-building-lighter-and-more-performant-vuejs-spa/ .
it’s using webpack’s magic comments https://medium.com/front-end-weekly/webpack-and-dynamic-imports-doing-it-right-72549ff49234.

@Q-Brad https://forum.vuejs.org/t/performance-penalty-of-global-component-registration/56655

Reddit says there will be a perf impact (no tests made) but it’s for you to decide to weigh in the tradeoffs, if you don’t register global reusable components then you’ll have to deal with import boilerplate code where they are used, especially if you’re gonna use the components numerous times. 100+ global components do sound a lot, personally I only register those that I will use heavily, usually form components.