They are just plain structs that your app wholly owns, so you can populate them with whatever you want!
chrismccord
Creator of Phoenix
Dmk
I’m using the setup from this guide: Multi tenancy with foreign keys — Ecto v3.14.0. From what I understand, using scopes would simplify things by removing some of the plumbing from that guide.
Is it correct that if I use scopes, I don’t need to manually pass org_id around or store it with Process.put? Would scopes essentially handle that part for me automatically? Just want to make sure I’m thinking about this right.
1
LostKobrakai
These approaches would be alternatives to each other. One using the process dict to implicitly retain the org context, or the scope struct to explicitly pass the org around. I wouldn’t call this “handle … for me automatically” though.
0
mayel
As a user of Surface who finds it really useful that the context/scope is automatically available in child components without having to include something like attr :current_scope, Scope, required: true and current_scope={@current_scope) everywhere, I had assumed that scopes would do something similar but is that not the case?
2
sodapopcan
It does but we speak of that when already talking about the router. %Scope{} itself can be considered a Phoenix Context so if would be much more confusing for it to named Context.
We’ve been using Scope at work for months now and it’s never confusing which “scope” we are talking about. However, “take a look at the context” would be far more confusing.
0
sodapopcan
No this is not the case. Scopes are just a struct that you can use to explicitly pass around “global” application data.
0
sreyansjain
Wow! Congratulations to Chris and team.
So many good things here.
The decision to include DaisyUI is very welcome.
Scopes put the right foundation for multi-tenant/SASS apps.
Very nice. More power to you!
2
gmile
bdarla
leejarvis
This isn’t a code configuration option (I had assumed that). Once you’ve signed in, you can go to the account settings and opt-in there. From a code perspective you could of course just remove the magic link code which seems straightforward.
2