[Snyk] Upgrade @vee-validate/i18n from 4.5.10 to 4.12.6

[denizd1]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @vee-validate/i18n from 4.5.10 to 4.12.6.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 58 versions ahead of your current version.

• The recommended version was released on 3 months ago.

Release notes

Package name: @vee-validate/i18n

• 4.12.6 - 2024-03-08
  

  🐛 Bug Fixes

  • Apply error messages again to prevent hoisted paths from being overridden 07d01fd

  👕 TypeScript

  • Expose Field component interface #4657
  • Updated valibot dependency #4658
• 4.12.5 - 2024-01-29
  

  🐛 Bug Fixes

  • Make sure removePathState removes the correct path state #4643 (#4649) thanks to @ bgoscinski
  • Remove event arg from define field handlers for component compat #4637 (#4647)
• 4.12.4 - 2023-12-27
  

  🐛 Bug Fixes

  • Check if both source and target objects are POJOs before attempting to merge them (2a09a58)
• 4.12.3 - 2023-12-16
  

  🐛 Bug Fixes

  • use spec object instead of checking tests for determining the required status of a field on yup schemas #4598 (#4599)

  🆕 Improvements

  • Remove deep data mutation warning #4597 (72e4379)
  • Allow path meta querying for nested fields #4575 (a18c19f)
  • Expose some state on form instance (e2171f8)
• 4.12.2 - 2023-11-29
  

  🐛 Bug Fixes

  • Apply schema casts when submitting #4565 (b2203c8)
  • defineField should respect global validateOnModelUpdate config #4567 (ec8a4d7)
• 4.12.1 - 2023-11-28
  

  🐛 Bug Fixes

  • resetForm not resetting unspecified fields to their original values if a partial is provided #4564 (36f6b9e)
  • resetField not setting the original value of the field causing the dirty flag to not update #4564 (36f6b9e)

  DX

  • unref initial values when initializing the form #4563 (c1c6f39)
• 4.12.0 - 2023-11-26
  

  💣 Breaking Changes

  Deprecated reactive initial values #4402 (bbecc97)

  Initial values can no longer be reactive since they did not serve any purpose for being so. The recommended API for setting async initial values is by explicitly calling resetForm.

  🆕 defineField API #4497

  This is a new function available on useForm and is meant to replace useFieldModel, defineInputBinds and defineComponentBinds by building upon and improving those APIs.

  <script setup>
  import { useForm } from 'vee-validate';
  
  const { defineField, errors } = useForm({
  validationSchema: schema,
  validateOnMount: true,
  });
  
  const [email, emalProps] = defineField('email', { validateOnModelUpdate: true });
  const [password, pwProps] = defineField('password', { validateOnModelUpdate: true });
  </script>

  <template>
  <input v-model="email" v-bind="emailProps" />
  <span>{{ errors.email }}</span>

  <input v-model="password" v-bind="pwProps" />
  <span>{{ errors.password }}</span>
  </div>
  </template>

  The docs have been updated to reflect using this new API instead of the deprecated ones. The old ones will continue to work till they get removed in next minor releases.

  🆕 meta.required

  Added support for meta.required state for Typed Schemas only.

  That means if you are using toTypedSchema helper with either Yup, Zod, Valibot, or Global rules then it should be automatically done for you. This is a new experimental feature and may not work well with conditional schemas or dynamic ones.

  For more info check the live demo link here.

  🆕 DX improvements

  • feat: add label support to defineField #4530 (f9a9584)
  • feat(DX): allow getters for field arrays paths (95b701f)

  🐛 Bug Fixes

  • Avoid overriding paths and destroy path on remove #4476 #4557 (f688896)
  • Clone values before reset #4536 (2abb896)
  • Handle hoisted paths overriding one another (e370413)
• 4.12.0-alpha.1 - 2023-11-05
• 4.12.0-alpha.0 - 2023-11-05
• 4.11.8 - 2023-10-05
  

  🐛 Bug Fixes

  • (perf) Avoid triggering extra model value events #4461 (d1b5b85)

  👕 TypeScript

  • Allow null as a valid Form prop type #4483 (78c4668)
• 4.11.7 - 2023-09-23
  

  💣 Breaking Changes

  • Removed default export from the @ vee-validate/rules package which caused issues for ESM importing #4470

  This only affects you if you are importing all the rules.

  Migration:

  - import AllRules from '@ vee-validate/rules';
  + import * as AllRules from '@ vee-validate/rules';

  👕 Types

  • useSetFormValues now accepts values generic type parameters (#4475) thanks to @ ivan-angjelkoski
  • Exported missing internal types causing a build error #4478 (a1414f6)

  🆕 New Features

  • Added Joi schema support thanks to @ lallenfrancisl (#4463), it was sneaked in a previous release tag but it is being announced here to acknowledge that addition.
  • Valibot and Yup schemas now merge their default values with the initial form values, allowing you to use each lib's schema defaults more freely (c372718)
• 4.11.6 - 2023-09-09
  

  👕 TypeScript

  This release is aimed at resolving #4421

  • useForm#defineComponentBinds is now more strict and provides accurate typings for both modelValue and update:modeValue properties. Previously they were not exposed.

  Try the following example.

  const { defineComponentBinds } = useForm({
  validationSchema: toTypedSchema(yup.object({
  date: yup.date().required(),
  number: yup.number().required(),
  string: yup.string().required(),
  valueModel: yup.string().required(),
  })),
  });

  const date = defineComponentBinds('date');
  const number = defineComponentBinds('number');
  const string = defineComponentBinds('string');
  const valueModel = defineComponentBinds('valueModel');

  
  


• 
  4.11.5 - 2023-09-09
  


• 
  4.11.4 - 2023-09-09
  


• 
  4.11.3 - 2023-08-23
  


• 
  4.11.2 - 2023-08-20
  


• 
  4.11.1 - 2023-08-01
  


• 
  4.11.0 - 2023-07-30
  


• 
  4.10.9 - 2023-07-30
  


• 
  4.10.8 - 2023-07-22
  


• 
  4.10.7 - 2023-07-16
  


• 
  4.10.6 - 2023-07-08
  


• 
  4.10.5 - 2023-07-03
  


• 
  4.10.4 - 2023-07-03
  


• 
  4.10.3 - 2023-06-29
  


• 
  4.10.2 - 2023-06-25
  


• 
  4.10.1 - 2023-06-23
  


• 
  4.10.0 - 2023-06-22
  


• 
  4.9.6 - 2023-05-31
  


• 
  4.9.5 - 2023-05-21
  


• 
  4.9.4 - 2023-05-17
  


• 
  4.9.3 - 2023-05-11
  


• 
  4.9.2 - 2023-05-09
  


• 
  4.9.1 - 2023-05-08
  


• 
  4.9.0 - 2023-05-07
  


• 
  4.8.6 - 2023-04-17
  


• 
  4.8.5 - 2023-04-15
  


• 
  4.8.3 - 2023-03-15
  


• 
  4.8.2 - 2023-03-14
  


• 
  4.8.1 - 2023-03-12
  


• 
  4.8.0 - 2023-03-12
  


• 
  4.7.4 - 2023-02-07
  


• 
  4.7.3 - 2022-11-13
  


• 
  4.7.2 - 2022-11-02
  


• 
  4.7.1 - 2022-10-23
  


• 
  4.7.0 - 2022-10-09
  


• 
  4.6.10 - 2022-09-30
  


• 
  4.6.9 - 2022-09-19
  


• 
  4.6.8 - 2022-09-19
  


• 
  4.6.7 - 2022-08-27
  


• 
  4.6.6 - 2022-08-16
  


• 
  4.6.5 - 2022-08-11
  


• 
  4.6.4 - 2022-08-07
  


• 
  4.6.3 - 2022-08-07
  


• 
  4.6.2 - 2022-07-17
  


• 
  4.6.1 - 2022-07-12
  


• 
  4.6.0 - 2022-07-11
  


• 
  4.5.11 - 2022-04-10
  


• 
  4.5.10 - 2022-03-08
  

from @vee-validate/i18n GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs