Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
@vee-validate/i18n
Advanced tools
Localization module for vee-validate
VeeValidate v4 breaks up the parts that made it a popular solution for form validation into it isolated parts. The core vee-validate
package no longer includes logic for localization.
This is where this package comes in.
yarn add @vee-validate/i18n
# or with npm
npm install @vee-validate/i18n
import the localize()
function from @vee-validate/i18n
which returns a message generator function:
import { defineRule, configure } from 'vee-validate';
import { required } from '@vee-validate/rules';
import { localize } from '@vee-validate/i18n';
// Define the rule globally
defineRule('required', required);
configure({
// Generates an English message locale generator
generateMessage: localize('en', {
messages: {
required: 'This field is required',
},
}),
});
If you have multiple locales in your application, you can add them like this:
import { defineRule, configure } from 'vee-validate';
import { required } from '@vee-validate/rules';
import { localize } from '@vee-validate/i18n';
// Define the rule globally
defineRule('required', required);
configure({
generateMessage: localize({
en: {
messages: {
required: 'This field is required',
},
},
ar: {
messages: {
required: 'هذا الحقل مطلوب',
},
},
}),
});
You can change the locale using setLocale
function exported by the @vee-validate/i18n
anywhere in your application:
import { setLocale } from '@vee-validate/i18n';
setLocale('ar');
To save you a lot of time translating @vee-validate/rules
messages to your language, the awesome community around vee-validate already contributed over 40+ languages that you can use directly in your application and get started quickly. The localized files include localized messages for all the global rules provided by @vee-validate/rules
package.
You can import the locales from their JSON directory like this:
import { configure } from 'vee-validate';
import { localize } from '@vee-validate/i18n';
import en from '@vee-validate/i18n/dist/locale/en.json';
import ar from '@vee-validate/i18n/dist/locale/ar.json';
configure({
generateMessage: localize({
en,
ar,
}),
});
You can view a list of the available languages by checking the locale folder
4.5.0 (2021-09-26)
Note: Version bump only for package vee-validate
FAQs
Localization module for VeeValidate
The npm package @vee-validate/i18n receives a total of 27,216 weekly downloads. As such, @vee-validate/i18n popularity was classified as popular.
We found that @vee-validate/i18n demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.