antilibrary hopefully the feature will be improved in time
_charts.html template don't output anything but just add that chart to a list. Probably, when rendering the extensions this doesn't transfer to the main template and hence the default empty list of charts is used. Don't know if that can easily be worked around or if the way the chart data is transferred would need to be changed.
@yagebu {{ charts.chart_data }} evaluates correctly within an extension.application.py for extension_report() includes these lines:344 return render_template( "_layout.html", content=content, page_title=extension.report_title)
and _layout.html contains:<script type="application/json" id="chart-data">{{ charts.chart_data|tojson|safe }}</script>
Extension methods have
begin and end arguments like so:FavaExtensionBase.extensionname(self, begin=None, end=None)1) These arguments are presumably dates? Do they come from the user selecting dates in the data selector in the UI? If I set them though, they're still
None when my extension is called. What gives?2) What's the calling method that sets them? Stack trace takes me to jinja, which can't be it
3) How should I be using these dates if I'm running a query via
FavaExtensionBase.ledger.query_shell.execute_query ?
hi, I have a question related to expenses aggregation and budget in fava: say that I have a number of expenses categories named Expenses:John:Media, Expenses:John:Groceries, Expenses:John:Clothing.
Additionally, I have a budget set for Expenses:John (using custom "budget").
In the Expenses view of fava, the aggregation per period (say quarter), does not seem to aggregate by sub-category in relation to the main category.
In other words, I would like to see the sum of all expenses for John compared to the set budget but I only see the subcategories spend but no use of the overall budget for John. I hope it makes sense :)
<script type="application/json" id="chart-data">{{ charts.chart_data|tojson|safe }}</script> in your extension template could work. But please do note that this might break, I consider the charts an internal implementation detail and want to keep the freedom to modify how they work.
