-
Notifications
You must be signed in to change notification settings - Fork 20
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
New fava version breaks fava-investor #84
Comments
Good to know, thanks for the references too! I'll get around to it when I can. Meanwhile, PR welcome from anyone. |
I'll take a look at it. Most modules work just adding the correct extension_name. There is a problem where g.ledger.price_map doesn't exist anymore. Now, it's called g.ledger.price, which returns a ~PriceMap called FavaPriceMap. This is the definition: link to beancount/fava. When fava-investor tries to convert positions to amounts in assetalloc_class here: permalink to fava-investor/assetalloc_class/libassetalloc, it uses the beancount API, which tries to inverse, which breaks the process. Look:
There isn't an obvious way to go from FavaPriceMap to PriceMap, so maybe we can get the amount without the convert_amount method? |
See this comment: With the latest fixes, everything works except for asset allocation by class, with which the display formatting is incorrect, and is missing the graph. I've opened beancount/fava#1721 for it. Help appreciated. #87 tracks that issue. Closing this. |
Hi! Apparently, v1.2.5 breaks fava_dashboards. For example, I've seen that FavaAPIException is not FavaAPIError in helpers.py.
I get this error:
werkzeug.routing.exceptions.BuildError: Could not build url for endpoint 'extension_report' with values ['bfile', 'module', 'report_name']. Did you forget to specify values ['extension_name']?
Reference:
The text was updated successfully, but these errors were encountered: