Description Usage Arguments Details Value Examples
Authorizes this package to interact with your Google Calendars. You will be automatically directed to a web browser, asked to sign in to your Google account, and prompted to grant permission for the package to interact with the Google Calendar service.
1 2 3 4 |
new_user |
Logical indicating whether to reauthorize using a new account and remove the current cached credentials. Currently, only one account can be authorized or cached in a directory at a time. |
key, secret |
Client key and secret for the application. See
below for more information on setting these in an |
cache |
Logical indicating whether to cache credentials in a
|
token |
Token object or the name of a token object |
verbose |
Logical indicating whether to print informative messages. |
Typically, users will not need to call this function explicitly, as
the authorization process will be triggered by the first action that
requires a user login. However, before using googlecalendar
,
the client credentials key
and secret
should be
predefined in an .Rprofile
file using:
1 2 3 4 5 |
Note that the default value of cache
may also be specified in
the .Rprofile
file using googlecalendar.oauth_cache
.
The recommended value is TRUE
.
For more information on obtaining these credentials, see the project README on GitHub or visit the Google API Console to get started registering an application.
An OAuth token object.
1 2 3 4 5 6 | ## Not run:
gs_auth()
gs_auth(token = readRDS("saved_token.rds"))
gs_auth(token = "saved_token.rds")
## End(Not run)
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.