Fava

------------------

It is now possible to convert to a sequence of currencies. Posting metadata is
now supported in the entry forms. The editor should now be a bit more
performant as the previous parses will be reused better. For compatibility with
extensions using them, the Javascript and CSS for the "old" account trees has
been re-added.

------------------

This release brings various improvements to the charts, like allowing the
toggling of currencies by clicking on their names in the chart legend. The
account balance trees in Fava are now rendered in the frontend, fixing some
minor bugs in the process and easing maintenance. Fava extensions can now also
provide their own endpoints.

------------------

With this release, extensions can now ship Javascript code to run in the
frontend. The editor in Fava now uses a tree-sitter grammar to obtain a full
parsed syntax tree, which makes editor functionality more maintainable and
should improve the autocompletion. The Flask WSGI app is now created using the
application factory pattern - users who use the Fava WSGI app directly should
switch from `fava.application.app` to the `create_app` function in
`fava.application`. This release also drops support for Python 3.7 and contains
a couple of minor fixes and changes, in particular various styling fixes.

------------------

With this release, the rendering of some report like the documents report has
been moved completely to the frontend, which should be slightly more perfomant
and easier to maintain. This release also contains a couple of minor fixes and
changes.

------------------

This release accumulates a couple of minor fixes and changes.

------------------

This release brings stacked bar charts, which are a great way to visualise
income broken down per account per month for example. The inferred display
precision for currencies is now also used in the frontend and can be
overwritten with commodity metadata.

The `journal-show`, `journal-show-document`, and `journal-show-transaction`
fava-options have been removed. The types of entries that to show in the journal
are now automatically stored in the browser of the user (in localStorage).

As usual, this release also includes a couple of bug fixes and minor
improvements. To avoid some race conditions and improve perfomance, the
per-file Ledger class is not filtered anymore in-place but rather the filtered
data is generated per request - some extensions might have to adjust for this
and use `g.filtered` instead of `ledger` for some attributes.