Release v2.4.0
18 November 2015
This is a sum-up of MANY improvements and patches released the last couple of months, which includes v.2.2.x and v.2.3.x too.
Changes
- added: Support for description field on events (also syncs to Google)
- added: [PUT] /events/:id - endpoint for editing both Google and non-Google events
- added: [POST] /events - now takes "my_rsvp" option to set initial creator response status
- added: [POST] /findtime - no takes "ignore_all_day_events" option to make all day events non-blocking
- added: [GET] /accounts/google/signup - you can now supply a custom callback (on the fly)
- added: [POST] /findtime/bulk - new endpoint to handle multiple findtime queries at the same time
- added: [GET] /users/timezone/:email - fetch a user's current timezone based on their email
- added: /credentials endpoints for creating and managing user API tokens (public exposure limited for now)
- improved: We've switched to using UUID's instead of random string as identifies for all resources
- improved: Shows full event details when using dynamic include on calendars
- improved: [POST] /findtime - can now use format "10:30" (and still "10") in timestamp filters
- improved: [POST] /calendars - returns full calendar object after creation (both Google and non-Google)
- improved: [POST] /calendars - when creating a Google calendar, name will be saved as display_name, since name is used for storing the ID from google
- improved: [POST] /calendars - calls Google sync after creating a calendar (only if a Google account is connected)
- improved: [PUT] /users/me - user can update own password
- improved: [POST] /findtime - better error message when trying to call findtime with a newly created user that does not have a calendar
- improved: [POST] /findtime - returns empty array instead of error when there is no available timeslots
- improved: [POST] /findtime - you can choose to query calendars and users by ID instead of email
- fixed: Fix timezones when saving events with Google
- fixed: [POST] /users/resetpassword - fixed a bug that made the endpoint unstable
- added: