Call to destroy for embeddable type does not work if embeddable type has policies about ash HOT 8 CLOSED

Locally, I just added authorize?: false to make my test work for now. I haven't had the time yet to investigate where the actor would be coming from.

from ash.

Maybe you already know where you would get it from or if it is even necessary, @zachdaniel. Otherwise, let me know, and I can investigate further.

from ash.

So, taking a look, I can see why this would be the case for the destroy call, but not the update call. I will push up a fix for the update call in a bit, and we can see if that resolves it for you.

from ash.

So, taking a look, I can see why this would be the case for the destroy call, but not the update call. I will push up a fix for the update call in a bit, and we can see if that resolves it for you.

I'm not sure I understand. Did you mean destroy in the second sentence? I'm also not sure what the difference is. Both are calls to actions that do not get the necessary data to run policies.

from ash.

What information are they missing (as of the latest?) I believe they are fixed.

from ash.

The actor

from ash.

We get the actor from the source changeset, because we copy the private context

from ash.

I guess that's happening in copy_source? I didn't check in there, because the variable passed in was called constraints.

I wasn't able to verify this yet because the newest commit kills my tests because of infinite recursion.

from ash.