Skip to content

fix: pass full context to Ash.load! in cascade changes #2537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jimsynz merged 4 commits into from
Feb 8, 2026
+14 −14
Merged

fix: pass full context to Ash.load! in cascade changes #2537

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
75ca83d
fix: pass full context to `Ash.load!` in cascade changes
jimsynz Jan 28, 2026
32ee606
fix: use scope option instead of to_opts for Ash.load! in cascade cha…
jimsynz Jan 29, 2026
8760e23
fix: avoid shadowing context variable in cascade changes
jimsynz Feb 1, 2026
d9b3462
fix: remove `authorize?: false` from cascade `Ash.load!` calls
jimsynz Feb 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions lib/ash/resource/change/cascade_destroy.ex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ defmodule Ash.Resource.Change.CascadeDestroy do

defp destroy_related([], _, _, _), do: :ok

defp destroy_related(data, opts, %{tenant: tenant} = context, changeset) do
defp destroy_related(data, opts, context, changeset) do
action = opts.action
relationship = opts.relationship

Expand Down Expand Up @@ -346,7 +346,7 @@ defmodule Ash.Resource.Change.CascadeDestroy do
|> List.wrap()
|> Ash.load!(
[{relationship.name, load_query}],
tenant: tenant
Ash.Context.to_opts(context)
Copy link
Contributor

@zachdaniel zachdaniel Jan 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can just do:
scope: context, but we should also do authorize?: false, so scope: context, authorize?: false to retain original behavior.

Copy link
Contributor

@barnabasJ barnabasJ Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wasn't authorized?: false removed intentionally in favor of having accessing_from set and having policies?

you didn't explicitly answer the question, but you merged the PR

Copy link
Contributor

@zachdaniel zachdaniel Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yeah you're right 👍 maybe a comment here saying that this is meant to run authorization.

)
|> Enum.flat_map(fn record ->
record
Expand Down
4 changes: 2 additions & 2 deletions lib/ash/resource/change/cascade_update.ex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,7 @@ defmodule Ash.Resource.Change.CascadeUpdate do

defp update_related(_, [], _, _), do: :ok

defp update_related(changeset, data, opts, %{tenant: tenant} = context) do
defp update_related(changeset, data, opts, context) do
action = opts.action
relationship = opts.relationship
copies = opts.copy_inputs
Expand Down Expand Up @@ -260,7 +260,7 @@ defmodule Ash.Resource.Change.CascadeUpdate do
|> List.wrap()
|> Ash.load!(
[{relationship.name, load_query}],
tenant: tenant
Ash.Context.to_opts(context)
Copy link
Contributor

@zachdaniel zachdaniel Jan 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

)
|> Enum.flat_map(fn record ->
record
Expand Down