[Snyk] Upgrade @vee-validate/i18n from 4.5.10 to 4.13.0 #239
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @vee-validate/i18n from 4.5.10 to 4.13.0.
ℹ️ 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 61 versions ahead of your current version.
The recommended version was released on 23 days ago.
Release notes
Package name: @vee-validate/i18n
🆕 Features
yup
schema contexts when using field-level rules #4753 (27fe5c8)setValue
on Field instance and slot props #4755 (ae3772a)ResetFormOpts
arg touseResetForm
#4707 (fd008c1)🐛 Bug Fixes
force
option not behaving correctly when passing empty objects or empty values, now it respects whatever you pass in as the new values and initial values #4680 #4729 (454bc45)all
export that contains all rules for@ vee-validate/rules
#4766 (fdb2d47)chore(release): publish
🐛 Bug Fixes
TypedSchema.describe
API crashing with future releases, now it just reportsfalse
formeta.required
(1376794)meta.required
for single field schema react to changes #4738 (1376794)meta.required
reacts to reactive form schema changes #4738 (c4415f8)🌍 i18n
🐛 Bug Fixes
👕 TypeScript
Field
component interface #4657🐛 Bug Fixes
🐛 Bug Fixes
🐛 Bug Fixes
spec
object instead of checkingtests
for determining therequired
status of a field onyup
schemas #4598 (#4599)🆕 Improvements
🐛 Bug Fixes
defineField
should respect globalvalidateOnModelUpdate
config #4567 (ec8a4d7)🐛 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
💣 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 #4497This is a new function available on
useForm
and is meant to replaceuseFieldModel
,defineInputBinds
anddefineComponentBinds
by building upon and improving those APIs.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
🐛 Bug Fixes
Important
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: