Skip to content
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

Google Calendar workflow is very difficult to set up #326

Closed
senorprogrammer opened this issue Oct 4, 2018 · 1 comment
Closed

Google Calendar workflow is very difficult to set up #326

senorprogrammer opened this issue Oct 4, 2018 · 1 comment
Labels
🐛 bug "Houston, we've had a problem."

Comments

@senorprogrammer
Copy link
Collaborator

senorprogrammer commented Oct 4, 2018

What's the problem?

It's nearly impossible to get the Google Calendar module working without reading the code to see what files need to be copied where, and how they need to be named.

The documentation is also wrong about where to put the final client configuration file (it now needs to live in ~/.credentials for some reason, because of tokenCacheFile()).

And for some reason the config file now needs to be named calendar-go-quickstart.json. Most of the configuration code needs to be stripped out and simplified.

How did you expect it to behave?

Get my credentials.json file, copy it to ~/.config/wtf/ and have the Google Calendar module just work. Instead I spent ten minutes trying to figure out what actually goes where.

Operating system

Terminal program & version

WTF version

@senorprogrammer senorprogrammer added the 🐛 bug "Houston, we've had a problem." label Oct 4, 2018
@senorprogrammer
Copy link
Collaborator Author

Effectively fixed by #327

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug "Houston, we've had a problem."
Development

No branches or pull requests

1 participant