¿Why are Mediatr request in the application layer?

[MatthiasMuller]

As I learned in the last months, Application project should contain only the implementations of what the request should do. In this boilerplate the application layer contains all the mediatr request and the logic behind them.
Why?

Thank you for your response.

[fretje]

Not sure what you mean... where else would you put them? It's definitely possible to put the requests in a separate "shared" library (so they can potentially be used by the front-end as well), but then they would still be part of "application", as application would still need to have a reference to them to be able to implement them. Remember, references (or dependencies) can only point "inward".

[MatthiasMuller]

Thank you for your response! I misunderstood some things about DDD and I was wrong.
Anyway, thank you for this awesome boilerplate, im using it to learn and understand DDD and good practices with dotnet.