v0.7+: $params values are null

[laurentpayot]

As you can see in the default fiddle the $params values are null:

{
  "text": {
    "required": false,
    "minLength": true,
    "$model": "",
    "$invalid": true,
    "$dirty": false,
    "$anyDirty": false,
    "$error": false,
    "$anyError": false,
    "$pending": false,
    "$params": {
      "required": null,
      "minLength": null
    }
  }

So using $v.text.$params.minLength.min like the docs say gives a type error.

This bug appeared in v0.7.0, it was working in v0.6.2.

[Frizi]

It seems like an issue only with the browser version, since all the tests are passing. I'll take a look and I'll add a test case for that.

[Frizi]

Fix released as v0.7.4

[Riplar]

Experiencing the same behavior with electron 3.0.8 and Vuelidate 0.7.4.

[larswww]

Same issue here

Experiencing the same behavior with electron 3.0.8 and Vuelidate 0.7.4.

+1!

[oxid72]

Same issue

[bartdominiak]

Can we reopen this issue? $params are null in 0.7.4

[kevintruby]

Also having an issue with $params object in 0.7.4, using Vue 2.5.21 in a Laravel application.

Not sure if this matters, but the application is being bundled by Webpack via laravel-mix 4.0.12 -- according to my package-lock.json file the version of webpack installed is 4.28.3.

Otherwise loving this library though!

Edit:
On further investigation, this doesn't seem tied to the version of vuelidate specifically. This jsfiddle of mine is using 0.7.4 with edge Vue and appears to detect parameters just fine. I don't know what kind of build tools anyone else here is working with, but I'm guessing the issue in my implementation might come down to how my application is being built.

Follow-up Edit:
The solution for me turned out to be super simple; anyone having this same issue (with a similar build process) might want to consider trying this change. My application was attempting to load Vuelidate as an application-wide plugin:

import Vuelidate from 'vuelidate';
Vue.use(Vuelidate);

But if I remove this code, and use the following in the form component that ultimately needs to use it, the $params work again!

import { validationMixin } from 'vuelidate';

export default {
    ...
    mixins: [ validationMixin ],
    ...
}

Using the mixin didn't work until I removed the application-wide plugin declaration. Hope this helps!

[mankey-ru]

Also started to experience same problem with 0.7.4 on Electron after "npm update" which did not involve Vuelidate itself.

I tried to downgrade several packages including vue and vue-template-compiler but no success: I could not manage to detect the exact update due to complexity of app.

Anyway, global injection of plugins is evil; now, with mixin injection (HUGE thanks to @kevintruby ), code looks and works better.

[BernhardSchlegel]

My issue was a different one: My import looked like

import { minLength } from "vuelidate/src/validators";

while it really should be according to the documentation - the auto import of Webstorm screwed me :)

import { minLength } from 'vuelidate/lib/validators'

[sun-lau]

same problem,$params value are null
faced on 0.7.6, browser-ready bundle.

The solution is include vuelidate.min.js before validators.min.js

[leonid-chernyavskiy]

This one needs to be on documentation or somewhere else (FAQ?)

Also, bug reappears when loading via async modules with webpack chunking enabled. Runtime selection of "withParams" would somehow make life easier:

src/withParamsBrowser.js, last export, change to:
export const withParams = function () { return (root.vuelidate ? root.vuelidate.withParams : fakeWithParams).apply(null, arguments); }