From 51e003e4f25a51a128a7669d657653df70c225b6 Mon Sep 17 00:00:00 2001 From: Barnabas Jovanovics Date: Mon, 8 Jul 2024 15:51:56 +0200 Subject: [PATCH] docs: fix call to for_read in auth docs (#1291) --- documentation/topics/security/actors-and-authorization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/topics/security/actors-and-authorization.md b/documentation/topics/security/actors-and-authorization.md index 15a77321..548c2923 100644 --- a/documentation/topics/security/actors-and-authorization.md +++ b/documentation/topics/security/actors-and-authorization.md @@ -35,7 +35,7 @@ MyDomain.create_post!(Post, authorize?: true) > # DO THIS > > Post -> |> Ash.Query.for_read(:read, actor: current_user) +> |> Ash.Query.for_read(:read, %{}, actor: current_user) > |> Ash.read!() > > # DON'T DO THIS @@ -51,7 +51,7 @@ The default value of `authorize?` is determined by the `authorization` configura ## Authorizers -Authorizers are in control of what happens during authorization. Generally, you won't need to create your own authorizer, as the builtin policy authorizer `Ash.Policy.Authorizer` works well for any use case. See the [Policies guide](documentation/topics/security/policies.md) for more. +Authorizers are in control of what happens during authorization. Generally, you won't need to create your own authorizer, as the builtin policy authorizer `Ash.Policy.Authorizer` works well for any use case. See the [Policies guide](documentation/topics/security/policies.md) for more. ## Domain Authorization Configuration