Not sure if the solution is ideal, but what I ended up doing was just setting a new variable and exporting like so:

let router = null; export default function({ store }) { const Router = new VueRouter({ scrollBehavior: () => ({ x: 0, y: 0 }), routes, mode: process.env.VUE_ROUTER_MODE, base: process.env.VUE_ROUTER_BASE }); // ...... router = Router; return Router; } export { router };

@incremental yes, it’s mentioned https://quasar.dev/quasar-cli/boot-files#Introduction.

@tini You must connect to the DB from a server side nodejs, php, python, etc script. Then have your Quasar app connect to that script to do basic CRUD operations.

@grettel-guerrero can you ask this in quasar discord’s app-extension channel too https://discord.com/channels/415874313728688138/551066279943995397, so jeff could see it.

@rajatpage use header-selection slot and make it so that when selected scope property is true then you push all your row data to your components selected array.

I tried Vue transition and transition-group, is=“transition” and is=“transition-group” and none of them worked.
I can not even add new rows with simple fade-in-down animation.

I had done it on other frameworks, but it not works in quasar.

Autocomplete is a native browser feature, which is what qinput’s wrapped native input does.

@jhon

Maybe quasar’s cookie plugin allows duplicate keys? What if you first check if the cookie key exists before doing cookies.set?

See here:
https://quasar.dev/quasar-plugins/cookies#Verify-if-Cookie-is-Set

I read it here https://github.com/vuejs/vue/issues/7788 and the explanation about strict shows that it does just that - looping inside everything.

I don’t have any watch function in this regard, all other dispatch calls are going through with no problem, no breakpoints were breaking the execution so only that specific dispatch call was executing when the error occurred. Unless someone has something in his sleeve, I’m out of magic 🙂

@beets Thank you for your response

This is a great idea

https://wordcounter.tools

SOLVED (work around): Back ground for splash screens in Icon Genie

The task: Get all necessary splash screens from one single background picture with icon genie where all splash screens show the same picture.

The Interaction with icon genie: Icon Genie places a background picture centered in the middel of the splash screen. Too large pictures are not scaled down and will therefore be clipped. Pictures that are to small in height will be scaled up to have min. the height of the splash screen. Same for the width. Up scaling is done with the same factor in x and y direction.
Because splash screens have different height to width ratio there will be some clipping of the (scaled) background picture.
You must provide a background picture with your visible content in the center part and margins around that may be clipped away for some splash screens.

The work around:

Create a picture with the smallest height of all splash screens (in portrait mode this is 1136 px) and with approx. 900 px width. (It is the smallest height because icon genie only scales up but never scales down.) Fill the picture with your splash screen background color. Place your content in this picture and center it horizontaly. Your visible content should not have more than 500 px width. The left and right margin of aprox. 200px will be clipped off by icon genie in some splash screen formats.
If you want icon genie to place the app icon on top of your background picture you should have an empty area in the center so that the icon not interfere with your background.

Your background picture therefore is 900 px width and 1136 px height. The part, that is visible in all splash screens is 500 px width and 1136 px height.

The width of the background picture of approx. 900 px and the visible part of 500 px is a little experimental. You may calculate these widths as follows:

Get the largest height to width ratio of all splash screens (in portrait mode this is 2.17 from 1125 x 2436). Get the factor for scaling the background picture up in height: 1136 --> 2436, that is 2.14 = 2436/1136. After scaling up, the visible part of your background picture is 1125 px in width. That is the width of the splash screen with largest ratio from step 1. Get the visible width of your background picture by scaling down the width 1125 / 2.14 = 526 px. (This is little more than the 500 px but it is ok to have a little margin to the edge of the display.) Get the smallest height to width ratio of all splash screens (in portrait mode this is 1.33 from 2048 x2732). Your background picture should be at least 1136 / 1.33 = 854 px in width. More doesn’t matter. (This is little less than the 900 px but it is ok to have a little more pixels in width for rounding and clipping.)

With a little more width of the background picture and a little less width of the visible content it is easier to get a working background picture in the first attempt.

This way I got my splash screens with a bottom line of text and logo and with an overlayed scaled and centered app icon out of a single background picture.

Have nice splash screens !

I found a solution if anyone hits the same issue…

Installed vue-print-nb from https://www.npmjs.com/package/vue-print-nb

Decluttered code sample…

<q-dialog> <q-card > <div id="print"> <q-btn v-print="'#print'" /> <MyComponent /> </div> </q-card>

You’re right, I just found this clear article simpler than the official doc : https://hasura.io/blog/best-practices-of-using-jwt-with-graphql
But at the moment, I can’t really test, because there are some bugs with RLuders JWT plugin and CORS…

@jhon You would typically use a logging engine like pino, winston, or something custom. Or, if you run your app through PM2, it would log the console.log by default. The terms above should give you some starting point to Google.

@Siddharth

Great you solved the issue.

This way we eliminated the need for wkwebview

If you don’t have wkwebview than you’ll use UIWebView(default). Apple will (automatically) reject any webview based app uploaded to the iTunes store with code(used or not) that contains UIWebView.

Hi all,

Any chance that someone could know where it is coming from ?

Thanks,