Amichai Mantinband

Right, @IsItBroken gave the full answer ❤️ The difference is this line: https://github.com/amantinband/clean-architecture/blob/09605637026f5e05375969b4fedb6c797dabe736/src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs#L16 The entire process happens only after the user gets the response

Closing this issue. Feel free to reopen if you have further questions

Hey @NRichet! You can create a policy and enforce your logic there. I think you described the example policy I created of `SelfOrAdmin` which allows access to a resource to...

Nope, "Self" is "do action on my own resources". So user B can only make changes to user B's resources. Take a look at the `PolicyEnforcer` for the underlying implementation....

Closing this issue. Feel free to reopen if you have further questions

Hey @Risthart! You can definitely move the model validation logic to the presentation layer, and perform the model validation on the incoming requests, rather than the commands/queries. Regarding duplications, I...

hey @suugbut! The reason why the entities are not "dumb" or "simple" follows the "rich domain models" principle from Domain-Driven Design, which basically means - put as much business logic...

Hey @suugbut, as @Thijs153 wrote above - the presentation layer theoretically should not reference the Infrastructure layer. The only reason why it is referenced is for wiring together the interfaces...

I don't have such plans at the moment, but if others request this feature as well, then I will definitely consider it

Something like the following: ```csharp 10.Throw().IfOutOfRange(0, 100) ``` ?