Validator should check if it is being called on a user entity

After thinking about this some more, I think it makes more sense to inject the current user and then get the UID that way. With that approach, it doesn't matter whether the entity is a user entity or not.

In fact, injecting the current user is the wrong approach because it assumes that the user saving the user entity is always the same, which is definitely not the case (for example, when an admin edits another user's account). So I again propose the fix in the first post.

In fact, injecting the current user is the wrong approach because it assumes that the user saving the user entity is always the same, which is definitely not the case (for example, when an admin edits another user's account). So I again propose the fix in the first post.

You're right. This validator would be very hard to use sensibly on a non-user entity, however we tweaked it, and we don't do anyone a favour by allowing it.

I like that you used an exception here.

I've added a few nits on the MR, feel free to ignore.

ptmkenny → changed the visibility of the branch enforce_user_entity to hidden.

ptmkenny → changed the visibility of the branch enforce_user_entity to active.

ptmkenny → changed the visibility of the branch enforce_user_entity to active.

ptmkenny → changed the visibility of the branch enforce_user_entity to active.

ptmkenny → changed the visibility of the branch enforce_user_entity to active.

ptmkenny → changed the visibility of the branch enforce_user_entity to active.

Awesome working with you @ptmkenny :)

Automatically closed - issue fixed for 2 weeks with no activity.