May 0.32.0
Features
- User roles. Each account now carries a role that an administrator sets when creating or editing the user: Editor (full access, the default, and what every existing account keeps), Contributor (may record fuel fill-ups and charging sessions, everything else read-only) or Viewer (may see the data but change nothing). Administrators are unaffected and always have full access. The rules apply to the web interface, the REST API and the Home Assistant endpoints alike, and controls an account cannot use are hidden rather than left to fail. What an account can see is unchanged and still follows vehicle ownership and sharing. (#285)
- Notes and attachments on the vehicle timeline. Each timeline entry now shows the note recorded against it, and fuel logs and expenses list their attachments as links, so the timeline can be read without opening every entry in turn. (#284)
Fixes
- An odometer recorded against an expense, such as the reading taken at an oil change, now counts towards the vehicle's latest odometer. Previously only fuel logs, trips and charging sessions were considered, so registering maintenance left the last reading unchanged. (#286)
Other
- The API documentation page now describes what an API key may do under each role, and lists the
permission_deniederror code alongsideforbidden.
Upgrading
Roles are added by a database migration and default to Editor, so existing accounts behave exactly as before until an administrator changes them.