You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose a high-level "reports" subpackage which will massage the sqlite data to produce reports of consumption, trends, etc. The following would be useful:
A style profile of the current inventory, to see what styles are lacking
Most consumed drinks/styles within a date range
Fastest depleting drinks/styles ("first to go") within a date range
To keep things organized, the low-level API calls should continue to stay in abv/model, while high-level data processing and report generation would reside in abv/reports.
The text was updated successfully, but these errors were encountered:
Sounds good. I recommend keeping it built in such a way where the api package can consume the reports package to allow remotely querying the reports results
I propose a high-level "reports" subpackage which will massage the sqlite data to produce reports of consumption, trends, etc. The following would be useful:
To keep things organized, the low-level API calls should continue to stay in abv/model, while high-level data processing and report generation would reside in abv/reports.
The text was updated successfully, but these errors were encountered: