Open benjcunningham opened 8 years ago
This might not have been an API change after all; e400b41 (which pushed a few things that should have been in the failing build) seems to have things sorted out again without anything that directly addresses this issue. Need to write some more tests, but the real problem might just be a my misunderstanding of how dateTime
offsets and timeZones
interact with one another inside the service.
Seems like the API is behaving differently...
Specifically in
test-events.R
, we usegc_event_edit
to replace aYYYY-MM-DDTHH:MM:SSZ
-formatteddateTime
with aYYYY-MM-DDTHH:MM:SS-HH:MM
one. Note the change in how we specify time zone offsets.This was working before, but now the build is failing because the
event
object returned from the function gets offset by-HH:MM
, but gets formatted with theZ
instead.Have not found any Google documentation on a change yet, though.