I am working on a Laravel API project, and I am trying to build a dashboard with four simple reports. The reports get the data from different (already existing) models. So I was wondering where I should create the queries for those reports. Should I create a Dashboard Controller without a Model because I don't have a database table for the dashboard? Please advise me on the best practices for this specific case scenario. I want to keep the codebase clean, maintainable, and extensible.
Asked
Active
Viewed 274 times
1 Answers
0
For dashboard data ur gonna probably need relationships and other ways to get the data. What i most commonly do is make like HomeController, view and model and then upon user logging in that is default page and u display. I don't think doing it without model is gonna do you any better. With model at least u can clarify more clearly where is data coming from with ->relation than to use long code. Anyway, this subject is project specific so u need to determine what's best for you.
cile1993
- 156
- 10
-
As I said I am using an existing models in order to create the queries so I don't necessary need Dashboard Model as I don't have a dashboard table – Elisaveta Aug 23 '22 at 09:22
-
Yes but then there is where your decision comes to. Then u could just use controller and return a view with it. – cile1993 Aug 23 '22 at 09:25
-
This is an API so I can return a JSONResponse only – Elisaveta Aug 23 '22 at 09:25
-
dont u wanna style your dashboard? i know u can, i'm just saying what is most common use case. – cile1993 Aug 23 '22 at 09:27
-
1This is an API, the dashboard will be styled in the frontend. I am just sending the data – Elisaveta Aug 23 '22 at 09:33