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 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} })
}
}
gb-flag
not gb-flags
gb-flags
componentgb-flag
tag worked for me the corresponding image did not resolve.boot: [
...
'~@growthbunker/vueflags'
]
Am interested in this as will be hitting same challenge down the line.
Some thoughts:
You may like to consider SSR + PWA handoff.
https://quasar.dev/quasar-cli/developing-ssr/ssr-with-pwa
SSR shopfront knows subdomain through ssrContext
https://quasar.dev/quasar-cli/developing-ssr/configuring-ssr#Boot-Files
PWA shopfront knows subdomain through window.location
Code knows whether it is running client or server via process.env.CLIENT
and process.env.SERVER
Not a great comment mecjos. I am just a regular user of Quasar. Have found the support in this forum to be excellent. Much like the Quasar framework itself.
pagebus.js
).this.$on
is detected as error so am using $$on
instead.// file boot/pagebus.js
import { boot } from 'quasar/wrappers'
import mitt from 'mitt'
export default boot(({ app }) => {
app.use({
install: function (Vue, options) {
const pagebus = mitt()
app.config.globalProperties.$$on = pagebus.on
app.config.globalProperties.$$emit = pagebus.emit
}
})
})
If you wish to debug:
...
app.config.globalProperties.$$on = function (ev, ...args) {
console.log(ev, args)
return pagebus.on(ev, ...args)
}
...