How will Vue 3 affect Quasar?
Ben Hayat last edited by s.molinari
Any idea how Vue 3 will affect Quasar? Is Quasar going to affected majorly with the changes in Vue 3?
Hawkeye64 last edited by
Personally, I don’t think so. Everything should be backwards compatible. And, there will be consideration for writing or rewriting components with hooks, etc.
I also don’t feel qualified to answer as no one knows what exactly the future holds…
qyloxe last edited by
I brought this question because in one article I read that Vue’s team are working with 3rd party component vendors on V3 and changes that affect at component level. So I was hoping Vue has invited the Quasar to this gathering, so Quasar has the same info. as the other 3rd party. And if so, how will V3 would affect the Quasar system?
I also heard from someone who said Ionic has put the Vue implementation until V3 is close to release, as it affects their code.
Just trying to get heads up on this.
I believe Razvan is a vuejs community partner. I’m not sure how much weight that bears on influencing Vue 3 design decisions. I ve also read on the Vue forums that its intended for Vue 3 to be backward compatible, but Quasars pretty huge so who knows how it’s going to be impacted.
Imho, it seems a bit too early for Vue to do a python 2 on the community, it’s just got people on the boat I think pushing them off is a bit counterintuitive in their efforts to grow.
Can we expect some sort of official roadmap statement on this?
We will be jumping on porting to Vue 3 when it is officially released.
We’re in the loop with the Vue 3 changes (obviously been invited to the private Vue 3 RFCs).
Initial assessment is that at this moment we’ll be able to port Quasar without having to change the public API. Worst case, we’ll need few small changes but nothing big and if this would be the case, everything’s going to get documented.
Thanks Razvan; The place I’m doing contract development, I had suggested to use Vue and Quasar for their Desktop & Mobile UI, as I’m building the REST API.
My question was from the comments that came up in the meeting, as it made sense to bring it up. I’m sure your reply will make them happy.
Thanks for speedy answer!
Interesting. Thank you.
Although Microsoft suffers good client library like Vue or Angular (although their future client Blazor might be ok with .Net 5 runtime), but when it comes to backend, EF and Azure functions and etc., they have a good solution which I’ve used .Net since 2005. With the new .Net Core 3 and upcoming 5, the Web API is getting faster and better.
If I had not invested so much in .Net, I’d go with Node. But I have zero experience in it to write production quality code.
Are you using Swagger or any Rest API standards or just your own approach?
We’re building our .Net Core API via Swagger / OpenAPI.
I’m actually re-writing an OLD WCF to Web API for ,net Core apps to consume it. Using Postman. When finished, I might use Swagger to create docs.