Best posts made by rab

@ebena

Use q-table with :data=“userData” and define userData as a computed property:

computed: {
    userData: function () {
      return Object.entries(this.user).map(([k,v]) => { return {key: k, value: v} })
    }
  }

Use quasar boot file:
https://quasar.dev/quasar-cli/cli-documentation/boot-files

Example in this post:
https://forum.quasar-framework.org/topic/5224/integrating-thrid-party-component

@Quasarman

1. Tag should be gb-flag not gb-flags
2. Library seems not to register gb-flags component
   https://github.com/growthbunker/vueflags/blob/master/src/entry.js
3. Although gb-flag tag worked for me the corresponding image did not resolve.
4. Btw (I think) you can register plugins simply with a direct reference in boot part of quasar.conf.js; e.g.

boot: [
    ...
    '~@growthbunker/vueflags'
]

@rulrok

Am interested in this as will be hitting same challenge down the line.

Some thoughts:

1. You may like to consider SSR + PWA handoff.
   https://quasar.dev/quasar-cli/developing-ssr/ssr-with-pwa

2. SSR shopfront knows subdomain through ssrContext
   https://quasar.dev/quasar-cli/developing-ssr/configuring-ssr#Boot-Files

3. PWA shopfront knows subdomain through window.location

4. Code knows whether it is running client or server via process.env.CLIENT and process.env.SERVER