-
Notifications
You must be signed in to change notification settings - Fork 63
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
Issue #141: Waybar subscription missed opportunity #142
Conversation
I sadly haven't had any time to write any tests at all :( |
A update to the README would be good too :) |
Ok, I've added a little something to the README. I've also tried to fix the linting issue but because I've never worked with vala before, I'm not sure I've fixed it or made it worse... let's see (to be honest, I wasn't sure what the error really was 😅). The code definitely works as I've manually tested it and, let's be honest, my contribution is not rocket science anyway 😂. |
Ok, done! All you said makes sense. I didn't realise the parenthesis had an space leading them. Anyway, it should work now 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
Out of curiosity, what is the process this needs to follow until it ends in a linux distro? Arch to be more precise |
Atm it's only officially supported in the AUR. I'm actually not sure about that... I'll maybe check it out if I have some spare time. It would be nice to only need to maintain the swaync-git PKGBUILD instead of maintaining both (if that's even how it works...). I'll open an issue :) |
Ah ok, cool. Thanks for your work! |
This PR includes the number of notifications in the text field when
swaync-client
is called with waybar subscription. (Issue #141)With this PR, the output of the command becomes like this (please, note the
text
field being non-empty now):P.S.: I couldn't find tests for this feature. Are there any?
Thank you!