How to reference the authenticated user with the entity that is going to be created

[abhimanyusinghgaur]

@amaster507

I have created a feature request to allow for both before and after rules on updates to handle this.

Hi @sourabhbagrecha, I guess this is the one @amaster507 is referring to:

The Need for Update auth after logic

Continuing the discussion from Mutations - Graphql: Is this still in development? I would like this to be in the auth directive itself and not stuck in a JS Hook. Right now I can prevent a user from adding content as another user with the add rules, but the user can add data as their own and then update it to belong to a different user. This is a security whole as we do not want to allow users updating data and removing them as the author and assigning somebody else to make it appear that the …

We will discuss and update if we plan to work on it, given we have @lambda now.