this is not clean architecture because as Uncle Tom said, it's the framework that is hidding the business for which the app is made. suppose if you have to add the functionality "view customers" how would you work on that?
goto src\presentation\component folder to add components
goto src\main\routes to add route
goto src\main\pages to add the page
goto scr\domain\usecases to add interface
goto src\domain\models to add the model
goto src\data\usecases to add use case
i haven't mentioned test cases. so you see the problem here? I'm constant jumping from one folder to another. when it comes to bug fixing it would be a mess to locate n fix it.
now consider an alternate approach.
i have a folder src\customers
i add sub folder view and have the page, components, reset api, interface, route models and test cases all in one folder. which once do you think is easier
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
this is not clean architecture because as Uncle Tom said, it's the framework that is hidding the business for which the app is made. suppose if you have to add the functionality "view customers" how would you work on that?
i haven't mentioned test cases. so you see the problem here? I'm constant jumping from one folder to another. when it comes to bug fixing it would be a mess to locate n fix it.
now consider an alternate approach.
i have a folder src\customers
i add sub folder view and have the page, components, reset api, interface, route models and test cases all in one folder. which once do you think is easier