Well… this is exactly what i was afraid off …

I remember when a lot of members already asked a long time before if it will be necessary or not to create a complete new project to upgrade to v1.0 and the answers were ‘no need’…

I just can’t rewrite my project from scratch it’s just too big … that’s why i aksed too in order to be sure that i will be able to upgrade to the v1.0 despite the fact my project is really big … If i have to check in the list you put here and replace/change/adapt steps by steps the components and so on, it will just never end …

Hi guys,

First of all, congratulation for this new awesome version of Quasar ! It’s just all what i was looking for to develop my project !
But today i really need your help guys…
My project is running with quasar 0.17 and today i wanted to upgrade to the last version 1.0 beta for the new features.
So first i upgraded the quasar-cli in global and then i started to compare a new project created with the new cli to mine previously created with the 0.17 version… After multiples errors related to the quasar.conf.js and babel that i fixed, now it build but the compile fails with 9 errors… The problem is that I don’t know what those errors are … As you can see :

How to know what those errors are or what is the best way to upgrade from 0.17 to 1.0 beta please ?

Thanks in advance !

Hi everyone !

I though about something and why not a new idea directly integrated in the ‘q-editor’ component ?

The idea is based on vue-at package that i needed to use for my app.

The problem is that it’s really hard to merge it with the current ‘q-editor’ to have the mentionable option inside the q-editor right now if i want for example to edit a text and tag something in it (not a link)…

Do you think it could be interesting to have this new option in the q-editor directly ? Or maybe in a totaly new component ?
After multiple searches on Vue topics and tricks i didn’t find any really good and easy to use feature to create that kind of component to tag or mention someone or something like Twitter or Facebook for instance… That’s why i allow myself to propose this new idea ! Because i really love Quasar and want to use it as much as possible !

I guess it has to be difficult and maybe that’s why it’s not already available on Quasar but it could be definitely a very good point to propose this !

What is your opinion ? Or maybe you know another library that maybe i missed ?

Thanks for reading and have a good day !

@bretonio it was fixed for me but i really don’t remember what i did i’m really sorry for that …

Hi !

I got this error after updating to the latest version of Quasar :

Uncaught (in promise) Error: Cannot find module './fr-fr' at eval (eval at ./node_modules/quasar-framework/i18n lazy recursive ^\.\/.*$ (47.js:33), <anonymous>:325:12)

I didn’t have it before and it looks like it’s because in the i18n of quasar-framework, it’s not ‘fr-fr’ but only ‘fr’ when this.$q.i18n.getLocale() return ‘fr-fr’…

I fixed it in an ugly way but is it a framework issue or is it normal that this.$q.i18n.getLocale() doesn’t return the same string as the associated folder in ‘/node_modules/quasar-framework/i18n’ ?

Thanks in advance for your help guys !

It’s a really good news ! Can’t wait to see it ! Just hope the upgrade from the 0.17 to the 1.0 will not be a complete refactor ^^ …

Hi @mate8070 ,
I don’t really understand what is your problem… can you show us the part of your code concerned ?

For my part, I had to remove the node_modules folder (previously init with yarn) and reinstall it but this time with npm.
Then it worked for me again…

I had the same problem with the 0.17.10… I tried to upgrade to 0.17.12 and still not working like you @ouaR … What is really strange is that it was working before for me and for some reasons (i don’t know yet) it stopped …

Hello @genyded

Thank you for your answer ! The problem with your solution is that the user in the v-if is define in the v-for under.
But thanks to you i found the fix ! I just had to move the v-for and the v-if in the <q-btn> like that :

<q-btn v-for="user in form.users" v-bind:key="user.id" v-if="user.isAdmin === true">
  <q-tooltip anchor="bottom middle" self="top middle">
    {{ user.firstName }} {{ user.lastName }}
  </q-tooltip>
</q-btn>

It looks like the condition on the QTooltip prevented the value (and reactivity) after an update (with a push) in the store.

Thank you again for your suggestion !