| Age | Commit message (Collapse) | Author |
|---|
|
Stop using the `google-calendar3` directory and secret file and use an
application-specific one.
|
|
|
|
When the `--verbose` flag is given, print the event summary and
description, time, conference info, and attendees.
|
|
If the `--email` flag is supplied, parse a Google Calendar email from
standard input and extract the event's eid from there.
|
|
A base64-encoded string I tested with didn't pass the regex test, and
was treated as an event ID even though it was an `eid`.
Instead of testing whether the input is a base64-encoded string with
regex, assume it's a base64-encoded string and try to decode it. If that
fails, assume it's a regular event ID.
|
|
Event invitation emails include event ids encoded as "eid"s. These are
base64-encoded strings of:
{event_id} {user_email}
Add a new function that decodes the ID from the base64 string if the
input ID is base64-encoded. Otherwise, return the input event ID.
|
|
Decided to parse command line options manually so that if multiple event
response status flags are passed, only the last one will be used.
|
|
|
|
Try out the `calendar3` API to get a single event from Google Calendar.
Mostly copied the example code from the `google-calendar3`
documentation:
https://docs.rs/google-calendar3/2.0.4+20210327/google_calendar3/index.html#a-complete-example
Modified it to get a single event, and to use the OAuth2 secret from
`~/.google-service-cli/calendar3-secret.json`.
|
|
With:
$ cargo init --bin
|
