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

Record API errors and show them to the user #7

Closed
deanishe opened this issue Jun 22, 2018 · 5 comments
Closed

Record API errors and show them to the user #7

deanishe opened this issue Jun 22, 2018 · 5 comments

Comments

@deanishe
Copy link
Owner

If authentication fails, the only indication is in the log file. Save error to file and show it to the user.

@nikitavoloboev
Copy link

nikitavoloboev commented Jun 22, 2018

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 ~/go/src/github.com/deanishe/alfred-gcal and ran go get ./... to get all the libraries. I suppose it doesn't have to be placed in ~/go dir but go get ./... won't work otherwise.

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 workflow dir and where alfred build will put the binary into workflow I can run.

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.

@deanishe
Copy link
Owner Author

The workflow has its own build script at bin/build. That builds workflow in ./build. That's the directory you link to Alfred.

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 secret.go.private file that is a copy of secret.go, but includes the API key. It swaps them before building, and back again afterwards.

@deanishe
Copy link
Owner Author

Have you looked into this, @nikitavoloboev, or should I do it?

@nikitavoloboev
Copy link

@deanishe Have been quite busy as I got an internship recently and learning JS/React now.

Would be nice if you added the change. I also haven't looked at new AwGo changes. I did however look into modd and it's awesome.

@deanishe
Copy link
Owner Author

I got an internship recently and learning JS/React now

Congratulations! Hope that works out well for you.

Would be nice if you added the change

No problem. Will. do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants