v0.2.0

Added

• API, Frontend: Resolve forecasts (i.e. decide which outcome was actually the
  correct one). (#154, #155)
• Frontend: Forecast details dialog that can be opened by clicking on the
  forecast title. (#296)

Fixed

• Frontend: Display more detailed error messages. (#173, #212)
• API: Ensure the forecast date values are logical i.e. created must be
  before closes which in turn must be before resolves. Existing data is
  automatically migrated to enforce this constraint. (#234, #264)
• Frontend: When adding a new outcome in the Add Forecast form the focus
  moves to that new outcome so you can start typing directly. (#161)

Changed

• API: Date values passed to the GraphQL API may contain any time zone, but
  they will always be converted to UTC in the backend and returned as such. In
  the web frontend everything is converted to the time zone of the browser
  before displaying it. Existing data is automatically transformed to use UTC. (#265, #264)
• Frontend: Simplify the Add Forecast form on the main page. (#233)
• Frontend: Prettify and simplify the forecast list.
• Frontend: In Add Forecast form show two outcome rows by default because
  making a forecast with a single outcome makes little or no sense.

Git history