[MGNLUI-3919] Refactor inline field in WorkspaceAccessFieldFactory into CustomField Created: 20/Jun/16  Updated: 29/Jul/16  Resolved: 28/Jul/16

Status: Closed
Project: Magnolia UI
Component/s: security app
Affects Version/s: None
Fix Version/s: 5.4.8

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: vaadin
Remaining Estimate: 0d
Time Spent: 7d 0.25h
Original Estimate: 5d

Issue Links:
dependency
is depended upon by MGNLUI-3838 Wrong ACL-validation results in Acces... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: Saigon 54
Story Points: 8

 Description   

For each ACL entry, we want to have a field deriving from CustomField<info.magnolia.security.app.dialog.field.AccessControlList.Entry>.
Such a typed field will allow us to refactor the validation logic from the save action to a Vaadin validator.

We don't rebuild the intermediate artificial Node/Adapter structure, but fill the new field directly with ACL entries (in factory).—We still need to pass this map of ACLs as a property of the Item, so that the save action can read it.

We keep the multivalue part "as is", in the factory (add/delete buttons).
We also try to keep the chooser opening "as is", in the factory.
We try to make the field generic to reuse it for URI Access permissions

  • settable permission options, optional access-type options, optional chooser pluggability

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