thecount2a
commented
3 years ago One idea to avoid having to make a super complex UI while allowing flexible reporting would be to allow custom reports to be defined by "argument files." To see what an "argument file" is, browse to the hledger manual https://hledger.org/hledger.html and string search the page for the string "argument file". If you put @FILENAME as a command-line argument to hledger, it will read command-line arguments from FILENAME, in addition to any that you manually pass.
My idea would go something like this: allow users to to define a particular "custom reports" directory in their nextcloud, just as the journal file and budget file is currently defined. Any files inside the custom reports folder would be scanned by this extension code and each one would be listed in the UI as a custom report, using the file name as a label. For instance, I could define a file inside my custom reports directory called "Monthly Food Expenses this year" and that file would contain:
balance
-pthis year
-M
-T
Expenses:Food
The nextcloud report runner would simply need to add the CSV output argument onto the command and then run it, since the nextcloud report runner parses CSV to turn it into a HTML table.
Additionally, if this idea works out well, we could even make the pre-canned reports be defined in a similar way, to allow users to customize the pre-canned reports or use them as a model for understanding how reports are defined.
37Rb
Let the user change dates, add filter criteria, etc...