Mantra, cross cutting concerns


#1

How should I deal with cross cutting concerns using mantra?

For example user privileges. There are modules such as user, module a (depends on user), module b.
Also there are application wide privileges, module specific privileges.

I don’t know how to structure/design/architect this. What would be the pest practice for complex scenario?


#2

I don’t know why no one has answered this question. I guess there isn’t any way?


#3

Hey, I don’t have a definitive answer for this, but you might find this answer helpful.


#4

Thanks, I think that putting the cross cutting logic in composer function and composing with it wherever required is really good approach.

But what about action level? For example, every user can view the component but only logged in users can do X and Y. I can only think of defining some action and call it in other actions.