A fix has been merged. Please update your Quasar CLI.

Dobromir
@Dobromir
Posts made by Dobromir
-
RE: vuelidate multiple error-labels
-
RE: vuelidate multiple error-labels
@reath I have made a PR to quasar cli that will fix the problem. Waiting on approval. Until then, tell me if the workaround above worked.
PR for reference - https://github.com/quasarframework/quasar-cli/pull/198
-
RE: vuelidate multiple error-labels
OK, I was wrong. This is a Quasar CLI issue, rather then an issue with my plugin. Will make a PR to Quasar, see if it gets merged. Essentially you could try the not ESM build, so instead of what you had do this -
import VuelidateErrorExtractor from 'vuelidate-error-extractor/dist/vuelidate-error-extractor'
Problem comes from the fact. that there is a package, that uses an older version of a dependency the error extractor has. Because I do not bundle the deps in the ES module build, this happens. A properly configured webpack config should fix this
-
RE: vuelidate multiple error-labels
Found the issue. For some reason the bundled package for accessing deep object properties was returning undefined. Will fix it now and push a release.
-
RE: vuelidate multiple error-labels
that is fine, it works fine with any vue 2.x version. I had an old CLI version along with the new one I just had installed. Going to try to do things now
-
RE: vuelidate multiple error-labels
For some reason, Quasar is not loading my
quasar.conf.js
at all… I cannot setup the plugins. -
RE: vuelidate multiple error-labels
I will look into it today. Didnt get notified for the reply. …
-
RE: vuelidate multiple error-labels
@reath From what I am seeing in the codesandbox you attached, it all works. Is there an issue with Quasal when using its CLI?
-
RE: Progressive Button native styling and its Loaders.
Ok. Just wanted to give a helping hand
-
Progressive Button native styling and its Loaders.
Hey. Are there any plans to make the progressive loading buttons closer to the native ones, material having those round spinner etc. If not, do you need any help with that?
Also, and this is just an idea, could we at some point, have astart
,done
,error
methods on the intermediate so it can go back to its default state after X amount of time? I know I could run a timeout on my “progress” prop and set it to 0, but it can get a pain, I would have to extend the quasar button with my own button to not write it everytime.
On a side project of mine I implemented pretty much the same because I couldn’t use quasar there and it is really useful for Ajax calls and what not.