RicoTrevisan
Thinking out loud so that you can give me feedback if I got this correct.
I can use Scope both to make sure that the calls I’m making are properly scope and I can use it to have a few handy things at hand on each different LiveView.
So, if I take the example from the docs.
defmodule MyApp.Scope do
defstruct [:current_user, :current_tenant, :locale]
defimpl Ash.Scope.ToOpts do
def get_actor(%{current_user: current_user}), do: {:ok, current_user}
def get_tenant(%{current_tenant: current_tenant}), do: {:ok, current_tenant}
def get_context(%{locale: locale}), do: {:ok, %{shared: %{locale: locale}}}
# You typically configure tracers in config files
# so this will typically return :error
def get_tracer(_), do: :error
# This should likely always return :error
# unless you want a way to bypass authorization configured in your scope
def get_authorize?(_), do: :error
end
end
current_user and current_tenant should be the :id , correct? Everything else I want to “carry with me” I should put in the :context.
I’m asking this because I initially started putting together a project and I thought it would be best to put the whole %User{} and the %Tenant{} so that I can access it all easily, but I’m not sure that’s what the rest of the community is doing.
So, if I want to have the tenant_slug with me at all times, I should modify the above example like:
defmodule MyApp.Scope do
defstruct [:current_user, :current_tenant, :locale, :slug]
defimpl Ash.Scope.ToOpts do
def get_actor(%{current_user: current_user}), do: {:ok, current_user}
def get_tenant(%{current_tenant: current_tenant}), do: {:ok, current_tenant}
def get_context(%{locale: locale, slug: slug}) do
{:ok, %{shared: %{locale: locale, slug: slug}}}
end
def get_tracer(_), do: :error
def get_authorize?(_), do: :error
end
end
Trending in Questions
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
franckstifler
current_userandcurrent_tenantare the stucts representing the actor and the tenant which should be applied.for the tenant, you can implement the protocol
Ash.ToTenantthat would transform the tenant to what is needed (id in case of attribute multitenancy, or schema name in case of schema multintenancy)franckstifler
I think for the tenant_slug you aredoing fine, as with the locale.
What is the use of the slug in your context? I would have taken it in tenant struct (tenant.slug) everywhere I need to use it.
But if you’re using a schema based multitenancy, just implemented the Ash.ToTenant protocol and return the slug in
to_tenant/2RicoTrevisan
Thanks! I’m going to give this a try.
I’ll set the scope with the %User{} and %Org{} instead of just the id to reference them. That way I can get rid of the slug – the %Org{} already has the slug inside of it. (I use the slug for navigation
/orgs/{slug}/stuff)