What is best way to upgrade/ migrate to new version of quasar? You suggested somewhere to do:
npm update quasar-framework
To me it seems this just updates the Node package, right? Whereas for upgrading to 0.9.1 there are different packages in package.json and also because of webpack 2 I think the whole build foldere scripts are probably changed…
So ‘how to do it properly?’ is my question.
Yeah, setting these and adding to class works. Via css setting color to .item > i.item-primary also works. My problem was more of a ‘not working hot-reload thingy’ it seems. Thanks.
Ha! Next step they will make a Vue standard template with Quasar!
For e2e might consider Testcafe (in place of Nightwatch):
Pros:
easy install
complete test harness
javascript ES2016 with (async/await)
flexible selector system
smart assertions with retry policy
reports
@s.molinari And easier to setup: https://alligator.io/vuejs/components-flow/
@krsyoung Looking into things I found it really is a browser thing (i.e. you can not have the screen always open at fullscreen and need the user interaction, or you have to go nuts hacking to every version etc.). I ended up ‘working around’ the problem. So no ‘real’ solution I’m afraid.
Maybe it would be nice to have this supported in Quasar as well?
https://materialdesignicons.com/
I tried using this within Quasar:
https://www.npmjs.com/package/vue-material-design-icons
but then the styling is off from the ‘normal’ quasar icons, and you would also have different html tags for the mdi icons.
@akaryatrh No this.$q.notify does not work in vue file also not when set properly in quasar.config.js with
framework: {
components: [
],
directives: [
],
plugins: [ 'Notify' ],
},
Any idea why?
Would be cool have this one ‘setup’ as well:
https://github.com/antvis/f2
see also:
https://medium.com/@SimaZwx/https-medium-com-simazwx-introducing-f2-c44fb4e74c2d