Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add i18n error message support for EmailField #6463

Merged
merged 3 commits into from
Jul 25, 2024

Conversation

vursen
Copy link
Contributor

@vursen vursen commented Jul 23, 2024

Description

The PR introduces EmailFieldI18n with methods for setting error messages and updates the EmailField's validation logic to show these error messages when validation fails.

Note

It's still possible to use the setErrorMessage method to configure a single static error message. This error message will be displayed for all constraints and will take priority over any i18n error messages that are also set. However, when more than one error message is needed, i18n should be used or manual validation mode should be enabled.

Part of #4618

Type of change

  • Feature

@vursen vursen marked this pull request as ready for review July 23, 2024 10:48
@vursen vursen force-pushed the feat/email-field/error-messages branch from 62c2670 to 7ec64a0 Compare July 23, 2024 10:49
@vursen vursen enabled auto-merge (squash) July 25, 2024 09:09
Copy link

sonarcloud bot commented Jul 25, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
17.3% Duplication on New Code (required ≤ 10%)

See analysis details on SonarCloud

@vursen vursen merged commit f3fcbcf into main Jul 25, 2024
4 of 5 checks passed
@vursen vursen deleted the feat/email-field/error-messages branch July 25, 2024 09:23
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with Vaadin 24.5.0.alpha6 and is also targeting the upcoming stable 24.5.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants