[MGNLFORM-76] field name, mandatory, validation, max input length and similar should not be i18n-aware Created: 12/Jan/11  Updated: 19/Jan/11  Resolved: 14/Jan/11

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File formI18nFields.png    
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

 Description   

In multi-language environments, when switching from the default language to a different one, the user is shown a dialog (see screenshot) with the possibility to create a locale specific variant for fields such as mandatory or max input length which, IMHO, does not make much sense. Furthermore, a field like fieldName in the dialogEdit is required which makes it necessary to specify a value for it. This is rather annoying as one would most likely use the default one and instead either needs to type it again or type a variant of it. In the latter case, this could cause errors wherever the default value of it is referred to (e.g. in confirmation emails. Alternatively, one would need to create duplicates [e.g. for freemarker templates] with the locale-specific fieldName).
Apparently it was MGNLFORM-63 that added i18n flags to every dialog's control even where they were not actually needed.


Generated at Mon Feb 12 05:36:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.