Is the timeline component still in for v0.14? I haven’t found it.

Also, @rstoenescu I really think you should release 0.13 as 1.0 and 0.14 as 2.0, the code and quality is there, there’s no reason to be shy about it.

I’ve started playing with vuelidate and, following the examples there, I’ve had a toast appearing on vuelidation failures. When spamming the Submit button, multiple toasts would appear, with a lot of delay from the initial click. I didn’t like that, so I wrote a plugin that will throttle all methods in components that have their name starting with “handle”, for example handleSave.

It’s my first “public” plugin, so I’m also looking for some feedback on the code.

import { Utils } from 'quasar'

function install (Vue) {
  Vue.mixin({
    beforeCreate () {
      let self = this
      let meths = this.$options.methods
      if (meths) {
        Object.keys(meths).forEach((k) => {
          if (!/^handle.*/.exec(k)) return
          let f = meths[k]
          meths[k] = Utils.throttle(function (...args) {
            return f.apply(self, args)
          }, 2000)
        })
      }
    }
  })
}

const inBrowser = typeof window !== 'undefined'

if (inBrowser && window.Vue) {
  install(window.Vue)
}

export default {
  install
}

Sorry, no worries, I was able to patch things on the Kinto side, using an event subscriber. I’ll add a ticket as a reminder. Anyway, it’'s just an edge case, where Kinto-attachment expects that submited forms only have “valid” fields, from its point of view, but quasar adds that field without an opportunity to tweak that.

I’m already using quasar-edge and I’m yet in early stages of developing my app, so I’m willing to test whatever you throw at us.

Not for the faint of heart, be prepared to browse the code to figure out what has changed. But that’s the interesting part, right? Quasar has very high quality code and is pretty much idiomatic vuejs, so you’ll learn a lot just by browsing its code.

Maybe something like this can help you? https://www.npmjs.com/package/vuex-localstorage

I’m developing something similar, but I’m using Kinto + Kinto.js for the storage part. That means modeling your entire application arround the Kinto storage, you may not want that.

@rstoenescu Very nice work with the field / input / input-group components!

@GameSomnic see https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L4

So basically, now you just toggle the left slot and fill it with whatever the sidebar you want:

https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L34

https://docs.npmjs.com/cli/link is the proper way, IMHO

@alegreiff use git perhaps?

@dewdad: I’m a newbie when it comes to npm / node, but what I do to use quasar dev is: make a separate clone of the quasar repo, run npm install / npm run build / npm link, then go to my project folder and run npm link quasar-framework. Although I think it’s possible to use the quasar-edge package instead of that?

Another way: you could treat the whole modal as an input. Pass a v-model to the modal and follow the protocol to signal its change (this.emit('input', value)), see the vue.js section on custom inputs

Sorry, no worries, I was able to patch things on the Kinto side, using an event subscriber. I’ll add a ticket as a reminder. Anyway, it’'s just an edge case, where Kinto-attachment expects that submited forms only have “valid” fields, from its point of view, but quasar adds that field without an opportunity to tweak that.

I’m testing Quasar’s v0.14 uploader together with kinto-attachment (an attachment plugin for Kinto storage) and there is a problem.

The problem sits with both Quasar and Kinto:

• in the uploader, there is a line:

form.append('Content-Type', file.type || 'application/octet-stream')

The form is then sent with xhr.send(form). There is no insertion point where that form can be further customized (so that I can remove the unwanted Content-Type field.

• in kinto (irelevant for this) there will be an error when not all form fields are processable.

I’ll address this problem to the Kinto maintainers, also, but there it may have bigger implications and that code be aligned with some package philosophy. Here, in Quasar, at least, maybe it’s possible to somehow register a “modifier” for the form, before it’s submitted? Or make the Content-Type field optional?

@GameSomnic see https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L4

So basically, now you just toggle the left slot and fill it with whatever the sidebar you want:

https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L34

Is the timeline component still in for v0.14? I haven’t found it.

Also, @rstoenescu I really think you should release 0.13 as 1.0 and 0.14 as 2.0, the code and quality is there, there’s no reason to be shy about it.

Maybe this can help you: https://play.pixelblaster.ro/blog/2017/03/02/analyse-and-optimize-a-webpack-vuejs-bundle/

http://quasar-framework.org/guide/app-linter-configuration.html