No More Posting New Topics!

Helper classes are in “node_modules/quasar/dist/quasar.css”

@Zol This was extremely helpful. Thank you!

@ncamaa I don’t know the svg specification very well, right now it supports the style and transforms tag. I’ll implement separated style properties later. If you find it doesn’t work for a particular icon, let me have it so I can figure out where I got it wrong.

Ok I think I found why this was happening. I apparently had a separately installed copy of vue-loader, which contained the update. Uninstalling that separate install (it was not needed) solves the problem.

@s-molinari Yes, I agree, backend API and client’s app should be separated, thanks for sharing your thoughts!

Hi, @VasuKuncham I like your solution in your pen. How can you use the same code in a single file component?

@metalsadman Noted, it means local storage is still the best choice in this case, thank you!

My backend API is constructed, I wonder if you can share your thoughts on my queries - https://forum.quasar-framework.org/topic/8081/cordova-mobile-apps-signed-builds-and-env-file , is it advised to break the app into two parts (backend API and frontend Cordova app) or is it fine to include both into a Cordova’s signed build? My concern is the .env file (with backend/db credentials).

Thanking you in advance!

I am having the exact same issue today and unfortunately introducing an integration platform like Mulesoft is not an option. I posted in the capacitor Discord channel today and it’s been crickets.

yes i think this is possible, do check out this link https://dev.to/codeguru_io/how-to-create-continuous-deployment-pipeline-for-quasar-app-in-under-5-minutes-using-aws-amplify-1ohi
If this framework is not suitable for your deployment, try other frameworks like the Akka framework. just putting it out there. you can ignore it if you think otherwise

thanks @dobbel

Muchas gracias…

@s-molinari Thanks Scott! 😁

Hihi… learned something new with this. Vue adds the component instance to an array element in a v-for with refs. So, you have to access the first element of the array to get the underlying component internals. Yet, if you set a ref outside a v-for loop, the instance is directly on the named element of the $refs array. Hmm…

Getting back to your challenge… name isn’t a QBtn property. If you add it additionally, it’s an attribute. Check my codepen now, if that is what you are looking for.

https://codepen.io/smolinari/pen/YzpoBdR?editors=1010

If not, I’d tend to believe you are trying to accomplish something that is not standard practice with Vue. If you’d explain your use case better, we might be able to help you find the right path to a better solution.

Scott

@jj

If you want better support please create a working codepen.io that demo’s your problem.

@metalsadman
Thanks a Lot 🙌
It helped me.

@dobbel

Tks dude! I will read this part of doc to learn more.