Changes between Initial Version and Version 1 of Ticket #4637, comment 3
- Timestamp:
- 07/30/2019 04:47:54 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4637, comment 3
initial v1 1 1 Just to confirm, we do store a `end_date` field for the `wporg_events` table and fill it correctly according to the WordCamp data-source, for example for WordCamp Brisbane (A 2 day event) the Database table looks like this: `{... "date_utc": "2019-08-24 00:00:00", "date_utc_offset": null, "end_date": "2019-08-25 00:00:00", ...}` 2 2 3 Adding the `end_date` field to the response (as done in [attachment:"4637.patch"]), or perhaps a `dates` field instead is possible, but you'll then need to raise a core ticket to actually use that data and work out a UI. 3 Adding the `end_date` field to the response (as done in [attachment:"4637.patch"]), ~~~or perhaps a `dates` field instead~~~ is possible, but you'll then need to raise a core ticket to actually use that data and work out a UI. 4 (edit: Removed second suggestion, `end_date` works best IMHO, plus it's set for Meetup events as it provides and endtime, ie. `2019-07-30 9:00:00 -> 2019-07-30 12:00:00`) 4 5 5 6 For others, the API responsible is here: