Mmmh in Firefox (instead of Chrome) the old page remains in view although the url changes inline with going back in history. Looks like it is not refreshing or something. Any idea (before I post a repo…)?
@AhsanAbrar Hi, like Scott indicated, the framework is pretty stable and usable as it is now. v1.0 will only mean a few features more and (probably) some very minor API changes that will be easy to upgrade to.
@dgk Hi, sorry for the late reply. It’s difficult to give a straightforward response. Having backend and frontend in same starter kit is not a focus for Quasar, as Quasar is pure frontend. What I’d suggest is merging the two starter kits, although it will be extremely hard since. Furthermore they use Webpack1 and we switched to Webpack 2… This will require a lot of thought.
@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.