Mass event creation

[benjcunningham]

Creating a ton of events at once really deserves a better blueprint for implementation than what little thought I've given it so far...

For reference, the CSV uploading described in Import events to Google Calendar is what we should be aiming for (by passing a data.frame or one of its relatives).

[benjcunningham]

Initial thoughts on gc_event_import() functionality: It should take a calendar and a table of events (as either a tbl_df or file path). It ought to POST a new event for every row in the data frame and return a vector of either event IDs or event objects.

Tentative action items:

• [x] Wire frame the function as described above.
• [ ] Method as described in #1 for coercing the "regular dates" we might expect to find in a CSV.
• [x] Build method to coerce a tbl_df row into the (hopefully sparse) list structure of a body argument in POST_resource(). This should not only consider the header names used throughout the regular API / this package, but also the CSV headers defined here.
• [x] Tests, starting with creating a few event CSV files.

[benjcunningham]

The basic functionality is pretty much tied together in 99e8d75. Opening the following issues to address some of the leftover ideas:

Regular event import headers – #10 Optionally take file path for CSV event import – #11