- Issue created by @MegaKeegMan
- πΊπΈUnited States MegaKeegMan
I did not mention in the original comment, but I was considering that we would not need a permission for create, given that I think someone who is allowed to edit a tracked field's parent entity should be allowed to create a value revision for that field.
- πΊπΈUnited States mlncn Minneapolis, MN, USA
My first thought is this is quite out of scope for this module since a major feature is that it does not need to override the form field widgets to do its work, it simply tracks things.
But it would make it easy to add this sort of restriction, which could and should live in a separate module, though this could provide an API to look up the information so you don't have to go straight from the database to get:
(value for a) delta -> revision it came from -> uid -> role
and then you could form alter the specific deltas (i have not grokked the rules for this as you can tell from my attempts to blank out our meta fields.
You would have to lock multivalue fields from changing positions in the form.
So any rules you want to work out regarding who can edit whoms could be done.