[MTE-13] SwitchableField used for the Link component will always persists any property set and thus doesn't follow the convention Created: 13/Apr/15 Updated: 19/May/22 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia Templating Essentials |
| Component/s: | models |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Unassigned |
| Resolution: | Won't Do | 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)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
When using default fields in dialogs empty inputs won't be persisted in JCR – removing existing values from fields will actually be removed. The switchable field (info.magnolia.ui.form.field.SwitchableField) and its transformer (info.magnolia.ui.form.field.transformer.composite.SwitchableTransformer) used for the link field behave differently: E.g. when setting an internal link and switching to external link afterwards (and also providing a value for both links), both link properties will be persisted in JCR. An custom transformer would solve this. |
| Comments |
| Comment by Roman Kovařík [ 19/May/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, |