All Versions
91
Latest Version
Avg Release Cycle
17 days
Latest Release
944 days ago

Changelog History
Page 7

  • v4.0.3 Changes

    December 05, 2020
    🍱 🐛 Bug Fixes
    • 🛠 fixed an issue where radio inputs values were stringified #3064 (3e0f9a4)

  • v4.0.2

    November 27, 2020

  • v4.0.1 Changes

    November 25, 2020
    🍱 🐛 Bug Fixes
    • 👉 Make sure to pass down native blur and input and change listeners to rendered Field input node #3048 (2526a63)

  • v4.0.0 Changes

    November 16, 2020

    vee-validate v4

    🚀 This marks the first stable release of vee-validate v4 🎉 🎉 🎉

    🚀 This release is only for Vue 3.0 as the API is completely new and while loosely follows the same footsteps of the changes added in v3, it takes heavy inspiration from Formik's validation API while keeping it Vuey! 🖖

    If I have to describe vee-validate now, it's a progressive form validation tool now with the sole aim to make building faster forms, much faster for developers. ⚡️

    This means the API is now stable and it's unlikely that any breaking changes will be introduced, however since Vue 3 adoption is still slow I didn't get to cover a lot of use cases but I'm fairly confident in the API at the moment.

    So if you have been on the fence about using vee-validate because it was in beta, now it's the time to try it out and let me know how the new API makes your forms easier/harder! ✅

    Migration Guide

    ⬆️ As for a migration guide, I recommend reading the docs as the API is completely new and needs a fresh look. Still, I will provide a short migration guide highlighting the major changes and the simplest path to upgrade, but it's not going to be straightforward.

    Not a lot of changes since the last beta

    🍱 🆕 New Features

    • ➕ added validate method to the Form component's template ref instance #3030

  • v4.0.0-beta.3 Changes

    October 06, 2020
    🆕 New Features 🆕
    • feat(breaking): Renamed immediate prop on the Field component and useField function to validateOnMount to better communicate its purpose (#2938)
    • feat: Added validateOnMount prop on the Form component and useForm function to trigger initial validation without having to provide initial values (#2938)
    🛠 Fixes 🐛
    • 🛠 fix: Avoid toggling checkboxes values on subsequent events #2936 (#2937)

  • v4.0.0-beta.2 Changes

    October 05, 2020
    🆕 New Features 🎉
    • ➕ added label prop on the <Field /> component and useField() function to allow swapping fields name prop with something friendlier to end-users. Already yup supports that by appending label to your validation chain. This only applies to global validators. #2831 #2932 (#2933)

  • v4.0.0-beta.19 Changes

    November 07, 2020
    🍱 🐛 Bug Fixes
    • 🛠 fixed an issue where globally registered component won't render with as prop #3014
    🍱 💥 Breaking But Cool Changes

    🗄 Deprecated the reset methods on Field, Form components, and useField and useForm functions, instead added a new:

    • resetField on <Field /> and useField
    • resetForm on <Form /> and useForm

    The new methods offer new DX improvements over the old reset API, including an automatic reset of values and the ability to change the initial values.

    Affected issues: #3015, #3004

    This is probably the last of the breaking changes and hopefully I will be releasing 4.0 very soon.

  • v4.0.0-beta.18 Changes

    November 05, 2020
    🍱 🐛 Bug Fixes
    • 🛠 Fixed an issue when rendering fields with v-for or loops and the order of these fields change due to splice or swap positions, the fields would not preserve their own values and will behave incorrectly.
    • 💅 Avoid watching rules of type function in <Field /> and useField to allow for more flexible higher-order functions style

  • v4.0.0-beta.1 Changes

    October 02, 2020
    🐛 Bug Fixes 🐛
    • 🛠 fix: avoid binding the value prop to input[type="file"] (02a2745)

  • v4.0.0-beta.0 Changes

    October 01, 2020

    🆕 New Features 🎉

    • ➕ Added validation trigger options validateOnXXX for controlling validation on these events: input, change, blur, update:modelValue (#2927)
    • 💥 Breaking 💀: Now vee-validate will no longer validate on input now, this is to prevent the default experience from being too aggressive and you can customize it with the validateOnInput option

    You can view the section documenting this behavior here

    🐛 Bug Fixes 🐛
    • [rules]: Fix file validators not handling empty values (8e2f3d4)
    • [core]: Unwrap the initialValue passed to the useField to prevent reciving computed props or read only ref (0298a92)