With Phoenix on a umbrella we lost the ability to join several functions together

[marciol]

Seems that are different approaches being discussed like this answer here:

Domain Driven Design diagram for Umbrella app

Pardon my ignorance but is there a technical reason for for adopting this type of organization: inventory ├── authorizers │ ├── collection_authorizer.ex │ ├── permalink_authorizer.ex │ ├── variant_authorizer.ex │ └── product_authorizer.ex ├── models │ ├── collection.ex │ ├── image.ex │ ├── permalink.ex │ ├── price.ex │ ├── product.ex │ ├── stock.ex │ └── variant.ex …

[stevedomin]

@michalmuskala

I usually try to style all the domain “mutation” functions in a similar way:

foo(resource_or_id, params, actor)

Hi @michalmuskala. Randomly stumbled upon this old post while browsing the forum. What is actor in the function signature above?

[michalmuskala]

That would be some kind of user or API client information - basically some data about who is doing the action that can be used for authorization and logging.

[stevedomin]

Makes sense. Thanks Michal.