-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish vuejs 3/quasar 2 migration #29
Comments
@nucle Is v2 compatibility in the works? How much work still needs to be done and do you need any help? (I was part way through upgrading our production application to Quasar v2 but realized this was missing so I can't, unless I replace QWindows with QDialogs.) P.S. - nice issue description 😄 |
Hi @jaredthirsk, When I maximize and then restore the window, it has a different width/height and position. Everything you need is in the next branch. So maybe you can take a look. I think in two weeks i can work again on it. BR, |
Any news ? BTW: current git build fails with
|
I've just started learning Vue and Quasar. I'm pretty excited to see this in Quasar 2 / Vue 3. |
@nucle How is it going? Are you healthy again? I'm trying out the next branch and trying to get it working (first time working on an extension), but the extension seems to be referencing its own private version of Vue, which causes a failure in setup() for getting $q or calling onMounted -- so something is wrong. |
Hello, @nucle, it has been a while since last update about V2, so i wonder how's going , and when do you release it ? |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: