I had some problems with the most recent upgrade - an error required me to delete the node_modules and .quasar folders and run npm install and quasar upgrade -i again.

All good so far, but there was a compile error which I am writing about here because I am sure it will catch others out.

The error was

SassError: semicolons aren't allowed in the indented syntax.

It turns out I had to remove the semicolons around my predefined colours in the quasar.variables.sass file.

After that everything was back to normal.

@ssuess That is just what I needed…thank you!

Is there any way to have more than 1 file containing translations strings for each language?

At the moment I have 1 index.js file for each translation, but I would like to break these into smaller files to separate, for example, strings that never change (like country names) with those that are more likely to change due to changes in the interface, resulting in having both an index.js and static.js file for each language.

Is that possible?

@metalsadman I am blocking more than 1 tab ahead, but I was hoping to use validation to stop progress, but it is only working for some fields and not others.

I have a large q-form around a stepper component, and when I make a validate() call, only some of the dynamically created fields which require input are flagged. All of the fields are custom variations of q-input or q-select, but I cannot work out why some of these correctly display as being required, when others do not.

If you tab through each the components, all works as expected, but if you jump to the next step of the process without tabbing, the user is not alerted of required content.

So I need to simulate a focus event on all of the components of a step to get this to work. Any suggestions how I could go about this or are there other ways to work around this?

The authors came back and said that this behaviour was expected, and that the inclusion of the quotes makes no difference to the outcome, which may be right, but it does add to the payload and reduces readability so I will suggest that they include this as an option in the future.

Now I have to find out how I can have multiple language files for each language, so I can have dynamic translations that need to be maintained by this program, and static translations (for things like country names) which do no change. Any ideas how I can have more that 1 js file in each language folder?

Actually I found a small issue with the output (the output files have quotes around the key values, even though they are not present in the source) and so I have asked the developers for clarification on how to resolve this.

Apart from that, i think this is a brilliant idea, very well executed.

@dobbel It is really very easy.

Follow the instructions here to set up internationalization
https://quasar.dev/options/app-internationalization

Sign up to the Localazy service to get your application keys

Add the localazy.json file to the root of your app with content like this:

{

  "writeKey": "[your write key]",
  "readKey": "[your read key]",
  
  "upload": {  
    "type": "js",
    "files": "src/i18n/en-us/index.js"
  },
  
  "download": {
    "files": "src/i18n/${lang}/index.js"
  }
  
}

(this is based on the folders created with the default i18n installation)

then use the commands:

localazy upload

check your translations and

localazy download

It is as simple as that.

I have answered my own question: all that was required was to use the file type js instead of json and it works beautifully.

Nice stuff!

I saw a demo of Localazy here: https://vaclavhodek.com/how-to-localize-vuejs-app-with-vue-i18n-and-localazy and I LOVE the idea of outsourcing my localisation via an online portal so I thought I would check it out.

I got everything working to a point, and before I contact Localazy - has anyone got their library working? From what I can see it is expecting a straight js file and so:

{
  "helloworld": "Hello World!"
}

works but the default format for a quasar language file:

export default {
  helloworld: "Hello World!"
}

Does not, and neither does the export have the correct header. I can use intermediate files of course (which is what I am doing for testing) but is there a more elegant way?

No pressure chaps - at least you know we were paying attention! It looked so good in the preview, I cannot wait to see what it looks like. I think the concept of BEX is really interesting for user engagement and cannot wait to dig deeper.

I have been keeping my eyes peeled for the release of QUiN that was showcased in the Quasar Conference, not only because it will be a useful tool, but because I am interested in using BEX in a project I am working on now.

What is the status?

@s-molinari A very nice idea. I will have a play.

Thank you!

There is one feature I would love to see added to the QTime component:

When using this for duration, rather than for time, it would be great to specify a unit to use as default. For example, if your usage would most commonly be in minutes, then rather than hours being the first input, minutes is displayed upon launch.

I am thinking of creating my own duration component, as my alpha testers have all raised this component as being least effective when used as a duration object. My design will features three concentric rings of hours, minutes and seconds. When and if I can work out how to create my own quasar components, I will share.

I use Google to generate my QR Codes. Check out the chart apis https://developers.google.com/chart/infographics/docs/qr_codes

@vadym-voitko Brilliant - thanks

I know this is an old thread, but I also need to incorporate Stripe routines into a Quasar package, and so I am wondering what is the current status. Can you incorporate Vue components into a Quasar build like the one mentioned in the previous post, or is it better to build it from scratch?

Anyone have Stripe and Quasar happily working together?

Hi Scott,

quasar upgrade -i

In the end I created a new project and moved the code across and so I am back up and running. I am new to the whole node.js/npm/vuejs world and so when it breaks, I am sometimes at a loss how to fix it. So much to learn.

That being said, Quasar makes this development a dream, and I will continue to shout about it at every opportunity.

If you are the same Scott that hosted the conference - Congrats!.. there was a lot in that I will be using - especially the BEX stuff which is extremely cool.

Thank you for your time.

Quasar Newbie here,

Today while trying to upgrade the CLI to the latest build, I encountered an file share error (I am not sure why) with the result that now my Quasar installation will not run or upgrade (when upgrading you get a
TypeError: Cannot read property ‘version’ of undefined, when running you get a UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘charAt’ of undefined).

I am not sure what is the best way to get everything back to normal…do I create scaffolding in a new folder and copy my source across, or is there a better way?

Another newbie here, and I found this post when encountering the same issue and your solution only registered the first load of a site. Instead, I recommend you set up Google Tag Manager (which was new to me and is a companion to Google Analytics, but NOT the same) as per the instructions below
https://fullstack-tutorials.com/quasar-framework/quasar-framework-google-tag-manager-and-analytics-setup-for-an-spa-website

Takes a little while to set up, and make sure you follow ALL of the instructions but works GREAT