[MGNLFORM-267] Form templates created by yaml don't work Created: 17/Jul/15  Updated: 15/Apr/16  Resolved: 28/Jul/15

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: backlog541
Remaining Estimate: 0.25d
Time Spent: 4h 20m
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLFORM-236 Html escaping of form fields should b... Closed
dependency
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: Config by file / code
Sprint: Sprint 3 (Kromeriz)
Story Points: 3

 Description   
  1. The first problem is that info.magnolia.module.form.templates.components.FormParagraph#setFormProcessors uses simple array which is not yet supported by yaml.
  2. info.magnolia.module.form.templates.components.DefaultFormDataBinder#getFieldConfiguration expect JCR configuration be in place:
  • A] quick fix is to return a default for escapeHtml in case JCR configuration is not there
  • B] proper fix is to get the configuration from new registries

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