-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Drupal] Change Event Date and Time handling #44
Comments
I haven't pushed to live site yet, oops, only one dash between year and month. |
I will close the issue when it is done |
Per our discussion on UTC yesterday, and the note about that the api request url doesn't include a precise time, I'm going to assume the API filters by local Eau Claire time. |
If we implement this change to match the balsamic administration ui then Dates are stored as y-m-d. Easy peasy |
Yeah makes sense, it simplifies a couple things for us. |
ok, it is actuall yyyy-mm-dd, like 2016-06-01 |
the admin end is pushed to live environment, now the consumer needs to be adjusted to match |
date: "2016-05-31", this json snippet shows today at 10:00am until 12:00noon |
Depending on the direction the conversation goes in #46 (comment). In either case that's another issue, and sounds like the core of this one is done, so I'll close this one. Feel free to re-open if I'm mistaken. |
To make similar to balsamics, I've changed the date to a year, month, date storage format.
This also makes searching by date much easier.
Example:
/api/events/2016--5-31
will return any event with that date.
The times are handled as integers now with an hour field and a minute field.
Also a duration field
The text was updated successfully, but these errors were encountered: