@fsgiudice Easiest way is to take a look on Github using browser. Example in your case: https://github.com/quasarframework/quasar/pull/315/files (Files tab shows all changes that are pushed for PR). Would be a rules of thumb to simply make another clone of Quasar each time you start something new OR roll back your own commits and sync to latest Quasar repo.
Btw, thank you so much for taking time for a PR. Really appreciate it!
@xenetics There’s no difficulty in setting the unit and e2e testing. Currently don’t want to release a half baked testing until I figure out a good way on making components which use VueRouter testable. That would be the last milestone.
@dgk It alway wise to be careful when starting on an new adventure
The Quasar.start, as far as I understand it, is a way to make sure that some of the mobile platforms are properly initialized (when needed), no magic just a way to give Quasar a change to init som stuff early. If you just make sure this is in you startup function, there is really not much to it.
Quasar is just components, BUT the layout filosofi here is to use the same layout on different platforms, and therefor quasar is able to help you most if it controls things like startup and layout (q-layout).
Regarding webpack … it is true that the cli version makes a rather large Webpack2 setup, but this is NOT at all necessary, I have a single file version using webpack 1.x (and i also use typescript) and this works just fine. What you need as a minimum, is stylus, babel and a few defines (PROD, DEV and __THEME).
The quasar build utility is just a wrapper, nothing magic just trying to be nice
So I understand you concern I have just been over all this myself
@dunsun Hi, are you specifying full routes for q-drawer-link? so for example “/task/edit”, “/task/add” etc? I think you may either specify “task/edit” or using a computed property for the routes? I need some more details please.
Looks like your connection to Quasar Framework was lost, please wait while we try to reconnect.