introducing beeAlfred

[giovanni]

Using Beeminder to track your goals? You might be interested in this workflow to manage and update your Beeminder goals.

Thanks – as usual – to @deanishe and @vitor for their guidance and templates. Feedback welcome!
https://github.com/giovannicoppola/beeAlfred

 

[vitor]

This makes no difference to functionality, but you might appreciate the insight. You have your last Run Script set to with input as {query} instead of with input as argv. You’ll find @deanishe often saying (and I agree) you shouldn’t really use the former but the latter. In this case it makes no difference because you’re not using an argument—you’re using variables—but there’s no reason to change the default (with input as argv) either. Also, you should probably be quoting ${slug}; in bash it’s always a safer bet to quote. Unless you want it to specifically break on spaces and make it multiple arguments.

[giovanni]

thank you so much @vitor for your feedback! I will make these improvements in my next release. I also plan to learn how to add your updater to my workflows  

[vitor]

4 minutes ago, giovanni said:

I also plan to learn how to add your updater to my workflows

 

Let me know if you have any questions, though it’s made to be easy to set up.

 

But you’re using @deanishe’s python library, right? That has auto-updating built-in.

[deanishe]

8 hours ago, vitor said:

That has auto-updating built-in.

 

It does, but it's much more restrictive (gotta use GitHub releases, semantic versioning) and is more effort to integrate.

 

@giovanni You need to remove the .pyc files and __pycache__ from the repo/workflow and add *.pyc and __pycache__ to your .gitignore. Those files shouldn’t be in the repo, and especially not the released workflow.

 

They’re bytecode files that Python generates automatically, so you don’t need them in there, and they’re Python version-specific, so you don’t want them in there, or your workflow will refuse to run on a different version of Python.