-
Notifications
You must be signed in to change notification settings - Fork 13
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
Record API errors and show them to the user #7
Comments
Hi @deanishe I wanted to add this change but I am curious what would you say the best way to work on some Go workflow is? Let's say I cloned this repo to What would I do next? I would think I would have to remove Alfred Gcal workflow I have now and use your script to symlink the workflow in ~/go to Alfred. Then use your build script and then I am not quite sure. Basically I want to start hacking on a fork of the workflow without messing things up. For my own workflows I use these guidelines and this tool that assumes that your source code is separate to the workflow items that go into What is your process in developing workflows like I am curious? Also what would be the best way to forking and making changes to the workflow be? Thank you. |
The workflow has its own build script at I normally develop using modd, which rebuilds the workflow when I change something. This one isn't so straightforward, though, because you need a Google API key, which isn't in the repo. The build script expects a |
Have you looked into this, @nikitavoloboev, or should I do it? |
Congratulations! Hope that works out well for you.
No problem. Will. do. |
If authentication fails, the only indication is in the log file. Save error to file and show it to the user.
The text was updated successfully, but these errors were encountered: