web: Filters are dropped when ledger file is reloaded #314

TomK32 opened this Issue Dec 28, 2015 · 2 comments


None yet

2 participants

TomK32 commented Dec 28, 2015 edited

Starting hledger-web -e today does limit the transaction to the current day as expected but after changing a file all future transactions are also shown.

The question is wether to write that -e today into the web opts input field (so the user carries it along and can change it) or (my personal perference) apply them when reloading the journal.


Isn't it a little misleading/confusing to show a filtered view without having anything in the search field ? Should command-line query arguments be shown there from the start ?


On the other hand, that would mean you can change/remove the initial filter, and can't enforce a limited view from the command line. Maybe it's better after all to treat a command-line query as a permanent invisible extra filter.

@simonmichael simonmichael added a commit that referenced this issue Apr 29, 2016
@simonmichael lib: after reloading a journal, also refilter it (#314)
After reloading a journal due to a file change, we now also re-apply any
query specified by the options.
@simonmichael simonmichael added a commit that referenced this issue Apr 29, 2016
@simonmichael web: preserve initial query when journal changes (#314)
The initial query specified by command line arguments is now preserved
when the journal is reloaded. This does not appear in the web UI, it's
like an invisible extra filter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment