[MGNLUI-3887] Generalize some usages of concrete Configured definitions Created: 24/May/16  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: devwl, fields
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
supersedes MGNLUI-3758 Remove usages of AbstractFieldFactory... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Story Points: 2

 Description   

Namely:

  • Make AbstractFieldValidatorFactory accept interface FieldValidatorDefinition param type
  • Remove usages of concrete ConfiguredFieldDefinition in complex-fields, use interface FieldDefinition instead
    • set readOnly-ness on local fields directly (vs. on sub-field definition)
    • acknowledging minor API incompatibility in MultiValueFieldDefinition#getField()'s return type (similar for composite)

I crafted these couple commits some time ago, they were considered to go with MGNLUI-3758, but I decided to kick them out to keep things simple (and safer on 5.4).

Commits can be seen on my branch (by the time I emit the PR)
https://git.magnolia-cms.com/users/mgeljic/repos/ui/compare/commits?sourceBranch=refs%2Fheads%2FMGNLUI-3758-remove-usages-of-abstractfieldfactory-s


Generated at Mon Feb 12 09:11:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.