Slim 4 Tutorial

Slim 4 Tutorial.md

Slim 4 Tutorial

https://odan.github.io/2019/11/05/slim4-tutorial.html

If you liked the tutorial, please click here on the star button: https://github.com/odan/slim4-tutorial

For technical questions create an issue here: https://github.com/odan/slim4-tutorial/issues

If you have Slim framework specific questions use: https://discourse.slimframework.com/

Write your comments / suggestions / feedback here 👇

@blacktornado I think it makes no sense to create a new $app instance, because per request there should be only one Slim instance.
If you have further technical questions, please create an issue here: https://github.com/odan/slim4-tutorial/issues

This is a great tutorial, thank you so much!

Is there any particular reason to separate the Read and Create into separate repositories and services? In this example, would it be against design patterns to use a single UserRepository containing both insertUser and getUserById methods? Similarly, is it suggested to not combine the Service methods into a single UserService?

Hi @marcusball Please note that this is not an Active-Record (anti-) pattern. The shown pattern follows Command–query separation (CQS) on routing level. So read and write access is separated. To respect the SOLID (see SRP) principles, the service class is responsible only for one specific task (use case) and not more.