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
publicPath matters for Webpack in determining if a resource is static or dynamic (dynamic meaning it’s handled by Webpack as an asset of your app) and you must set taking into account Vue Router mode (hash or history) as the two modes work differently in respect to URL path
Images in assets should be used as src="~assets/...." OR set a relative path to the file you’re specifing as source
Webpack + Vue has a limitation on what can be considered an asset of your app or a static. In order for your resource to be considered an asset (and be optimized and included by Webpack) you must NOT use Vue dynamic props (such as :src – note the dot in front of src for this HTML attribute). If you use a dynamic prop then Webpack won’t be able to know which asset you will actually use at runtime, so it skips it.
Webpack rule: when specifying the source, if this source starts with / then it’s considered a static. So <img src="/statics/my_image.png"> uses a static. If instead we omit / and write <img src="statics/my_image.png"> then Webpack tries to manage it as a relative path (to the file containing this tag) and include it as an asset.
As a general rule of thumb: if you want to include an asset, hard-code it in src WITHOUT using a Vue dynamic prop (making it :src).
Vue/Quasar components using images (like image gallery as an example) uses a binded :src for the images, so these images must be in statics folder. Due to Webpack + Vue limitations, you won’t be able to make Webpack consider them as assets.