[MAGNOLIA-7629] NPE in key generator logic when field name is null Created: 10/Sep/19 Updated: 11/Sep/19 Resolved: 10/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Epic Link: | UI framework: forms, dialogs, content editing |
| Sprint: | UI Framework 6 |
| Story Points: | 1 |
| Description |
|
Reproducible in contacts app reference implementation, in column renderer (I believe 'status`) we generate field components whose labels get automatically i18n-ized. Configuration of such fields is partial, some properties are missing. As result, NPE in info.magnolia.i18nsystem.AbstractI18nKeyGenerator#replaceColons occurs. Bad side effect is that the app wouldn't start at all in such case. |