[MGNLUI-5175] Ability to translate validation error messages Created: 02/May/19  Updated: 25/Jan/21  Resolved: 23/Jul/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.1
Fix Version/s: 6.2.3

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: 62-UI-1, i18n, maintenance
Remaining Estimate: 0d
Time Spent: 2d 3h 44m
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLFORM-314 i18n is not working for form module e... Closed
relates to CFGUI-122 Fix missing i18n label Closed
causality
dependency
duplicate
is duplicated by MGNLFORM-323 The validators conversion.message.err... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: UI framework implementation
Sprint: Maintenance 16, Maintenance 17, Maintenance 18
Story Points: 3

 Description   

Currently validation error messages are returned directly from the error source, it is not possible to translate them.

As customers want to translate the user interface, they also want these error messages to be translated.

Here is the original request from the Suggestion Box ticket: 

  • Using TextField and the "type" property (e.g. Long)
    • - name: navSortOrder
    • class: info.magnolia.ui.form.field.definition.TextFieldDefinition
    • type: Long
  • Editor enters some invalid data like "aaa"
  • Error message "Could not convert value to Long" is shown
  • This error message cannot be translated

There should be a way to change this error message.

    1. Dev note

ConfiguredFieldValidatorDefinition - needs to be marked i18nable. Key should not be hardcoded. 



 Comments   
Comment by Viet Nguyen [ 25/Jan/21 ]

We are currently not support this in 5.7.x version as reported in MGNLFORM-314.

Generated at Mon Feb 12 09:23:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.