Make Authorization Container
a Vendor container
#708
Mohammad-Alavi
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
If put authorization in the vendor directory, where should I write custom authorization code if some projects require it? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was thinking...
Maybe we can even extract the Authorization container and make it a vendor container. This way we can make the base Apiato even thinner!
The policies are a great way to enforce access control and roles & permissions are like a cherry on top and not needed always but can be brought in easily as a vendor container when needed!
I even though a bit about the implications of extracting it to a vendor container and:
My thinking behind this is to strip anything that is not necessary to start a project and let the use pull in the things that he/she really needs.
Remember when we had like 10 container in a fresh Apiato install? e.g. Setting, Payment. Now we have only 3. Do you feel the loss? I don't. And I can pull in e.g. Localization container when I need it as a vendor container. This will be the case with Authorization.
Your thoughts?
Beta Was this translation helpful? Give feedback.
All reactions