Use of ENUMs and repository pattern in this type of project is a good thing, looking at the long term goals of project. Foundation should always be strong (depending on overall focus of the project)
DTO I usually use regularly in my projects. It helps defining DTO of FE frameworks as well in Typescript or Flutter for mobile / React Native etc. DTOs I personally think is good if we create APIs only with laravel and FE in some other frameworks instead of using Laravel views. About Repository pattern I too think is overkill.. I mostly prefer simple SOLID with services binded to interfaces and reuse wherever I need to do DI. But in this project the LLD scalability can be huge in future with Repository pattern I believe. What say
![[LIVE] : ONE ลุมพินี 84 วันนี้!! คู่เอก "ก้องศึก vs เมืองไทย"](http://i.ytimg.com/vi/3kuzsAIDf1c/mqdefault.jpg)
Use of ENUMs and repository pattern in this type of project is a good thing, looking at the long term goals of project. Foundation should always be strong (depending on overall focus of the project)
DTO I usually use regularly in my projects. It helps defining DTO of FE frameworks as well in Typescript or Flutter for mobile / React Native etc.
DTOs I personally think is good if we create APIs only with laravel and FE in some other frameworks instead of using Laravel views.
About Repository pattern I too think is overkill.. I mostly prefer simple SOLID with services binded to interfaces and reuse wherever I need to do DI. But in this project the LLD scalability can be huge in future with Repository pattern I believe. What say
Expected to see some timestamp info in the event. Otherwise how would you track impressions today Vs yesterday?
Great review. I will give it a try
When I build my open source in an organized way, is this a good thing?
Yes?
The answer to your question is so obvious!
It is a good thing in general too. Not just for open source.
@@LaravelDaily lmao