v0.36.0

0.36.0

Fuel consumption is now worked out one fuel at a time, so an AdBlue refill
logged against a diesel no longer distorts that diesel's figures.

Added

• AdBlue/DEF as a secondary fuel type. The fluid a diesel tracks alongside
  its fuel can now be named rather than logged as "Other". It is an exhaust
  additive rather than a fuel, so it is offered only as a vehicle's secondary
  fuel type and counts as no tailpipe CO2. (#319)
• The fuel log list shows the fuel type of each entry. (#319)
• Fuel logs returned by the REST API carry a fuel_type field, and every point
  of the vehicle stats consumption series is labelled with the fuel it belongs
  to. Fuel type stays read-only over the API: a log created there takes the
  vehicle's own fuel type. (#319)

Fixed

• Consumption is calculated per fuel type. The full-tank lookup, the litres
  counted in between and the consumption average all consider a single fuel,
  and the Fuel Consumption Trend draws a separate labelled line for each. An
  AdBlue refill on a diesel therefore never lands in that diesel's L/100km.
  Logs recorded before the fuel type selector existed count as the vehicle's
  own fuel type, so existing histories read as before. (#319)

Other

• The built-in API documentation now shows the fuel_type field on fuel log
  responses, and its list of selectable vehicle fuel types is complete again —
  it had been missing plug-in hybrid, hydrogen, E85 and other.

Thanks to the reporter of #319
for the clear description of the problem.

Upgrading is a straight version bump: no migration and no configuration change.