[MGNLUI-2218] An i18n text set directly in a dialog configuration should override anything else Created: 03/Oct/13 Updated: 17/Oct/13 Resolved: 03/Oct/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.1 |
| Fix Version/s: | 5.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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
|
||||||||||||
| Sprint: | 5.1 - Final | ||||||||||||
| Description |
|
"Trying to set the label of a blossom dialog to "Text", FormDialogPresenterImpl#buildView refuses to do that because it thinks that "Text" is a message key." This is is due to a hack handling unfound keys and avoid displaying keys themselves. Waiting to solve properly the problem (see related issue) the workaround can be made more lenient by assuming that a message key contains at least one dot. That should solve 99% of cases. |