What about removing the entry when removing the last permission? The unclickable (x) when there's just a single permission is a bit weird.

Or it could be greyed-out (and excluded from the value) sinc, but that'd add some extra complexity because you'd need to keep track of this in local state unless you just ignored empty entries on the server side (that'd already get rid of them after submission). But having this kind of transient state would also be convenient when adding someone new since you wouldn't need to assign some permission immediately.

Something in the value isn't 100% consistent. When I add a new permission and remove it again, the save button doesn't get disabled again, so the old/new value aren't equal.

Edit: Looks like it;s just missing isEqual={_.isEqual} on the <FinalField> (maybe it'd be best to provide a FinalACL component that takes care of it like I did for the PrincipalField)

What about removing the entry when removing the last permission? The unclickable (x) when there's just a single permission is a bit weird.

Or it could be greyed-out (and excluded from the value) sinc, but that'd add some extra complexity because you'd need to keep track of this in local state unless you just ignored empty entries on the server side (that'd already get rid of them after submission). But having this kind of transient state would also be convenient when adding someone new since you wouldn't need to assign some permission immediately.

Already suggested by @mic4ael 😉 , but thanks!

Something in the value isn't 100% consistent. When I add a new permission and remove it again, the save button doesn't get disabled again, so the old/new value aren't equal.

Edit: Looks like it;s just missing isEqual={_.isEqual} on the <FinalField> (maybe it'd be best to provide a FinalACL component that takes care of it like I did for the PrincipalField)

Solved!