Looks like we are in the same boat. @jolyon I am, however, working slowly but surely towards that goal. But, if I can influence others to get it done faster, that is also what I’ll do (and why you see me in such discussions often).
Click operation can be bound to the primary route , Add-on routes can be configured to take up the same target selection. I will probably change it to be a nested route instead , Should resolve the issue . The problem now is that , it has been configured as a separate route and I want the same tab to be highlighted .
Ah, but in your situation, why don’t you use a simple list without the q-drawer-link? DrawerLink (as its name implies) is supposed to get you to another route. Its HTML template is just syntactic sugar over a list item with the additional handling of route change.
During development it might happen because of HMR. Best would be before updating source files to close the Modal. This way HMR will correctly do its job.
In production this scenario can’t happen, so no bugs for final product.
I started experimenting with Quasar in sept 2016, and it’s been fun building stuff with it.
Never had any major problems, code quality and documentation are outstanding, and the developer is very responsive/approachable.
I’m currently doing internal alpha tests with my app in AppStore and PlayStore. Won’t be long before going beta.
Here’s a link to give you an idea.
Design is not polished/final. There is lot’s of freedom to customise. Either for both ios and android, or for each platform specifically. https://www.youtube.com/watch?v=u0UYSFLV6As&t=18s