syrian-open-source / hotel-management-system Goto Github PK

I recommend separating the project parties into repositories for each folder
so we can see like this:
for the backend, create a new repo called "hoter-management-system-backend"
for the frontend, create a new repo called "hoter-management-system-frontend"
for the mobile, create a new repo called "hoter-management-system-mobile"
and so on ..., these repositories basically helps us to develop requirements better and also helps to organize the work of developers more
Because sometimes it is possible only for frontend developers to work on the front part and backend developers develop the backend part and so on.

Thanks for you're heart work !!

• You should use a validation class for each request that requires the validation part, just like the UserRequest class
• Every request class should extend a base class called BaseRequest, and this base class should have all duplicated functions like failedValidation() and failure functions to handle the validation error response
• I think it is better to handle the error messages through the translation file in case you do not have any private message you want to return