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

:type appears to be a symbol, not a string #18

Open
mikelococo opened this issue Dec 15, 2015 · 1 comment
Open

:type appears to be a symbol, not a string #18

mikelococo opened this issue Dec 15, 2015 · 1 comment

Comments

@mikelococo
Copy link

Type is documented in several places as being a string:

And sometimes referenced as a string:

urgency: opts[:urgency] || (opts[:type] == "failed" ? :normal : :low)

Whenver I snoop on the values of type, they look like a symbol though. You may wish to update the docs and tweak that libnotify priority switch if they're intended to always be symbols.

@e2
Copy link
Contributor

e2 commented Dec 16, 2015

I'm not that much of a fan of documentation, really. And I don't use notification much, either.

(I'd actually remove the internal documentation, unless it documented something really surprising).

I guess it's intended to be a symbol:

[:failed, :pending, :success].include?(image) ? image : :notify

No one complained yet really, so if you can create a PR, I'll gladly pull it in.

I think the libnotify should be fixed to use fail, so the priority can be shown properly. I think of it as an enhancement, so no compatibility problems here.

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

No branches or pull requests

2 participants