-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] Statistics enhancement - Spent per member per month #58
Comments
Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
Thanks for the suggestion and for the love! I like the idea and it was quite quick to implement. There has been some changes in the line chart style, datasets are not stacked anymore and colored areas are not drawn anymore. Those line charts are more classic (and readable) now. I'm interested to know what you think about those changes if you get to try the nightly. |
Astounding! Thanks for the quick reply. I tried myself by forking the project and I saw the Statistics part is a bit 'hard-coded' and started myself to see how could I create a PR for this, didn't have time to fully understand the structure of the 'stats' variable and its content though. Anyway, thanks! I'm running Nextcloud with Again, thanks a million! |
Feel free to reopen if this feature does not properly work. |
I updated the latest version a while ago, finally got a chance to take a look into this and I've to say: BIG THANKS! It works flawlessly and now makes tons of sense. Thanks for hear me out and implementing this new feature request. You are a gent! |
Request for the addition of a new table + graph of a
Spends per member per month
in the Monthly stats per member existing sectionThis will bring a bit more value to determine who spends more or less regardless who has paid for it. Existing Global Stats already displays the total sum of this per member, however this is not reported in a monthly basis in in details below.
Thanks!
PS: amazing job! I fell in love with this app! Keep going the good work!
The text was updated successfully, but these errors were encountered: