💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

Finally - it would help if you could open a bug report and link to this PR to shed more light on the issue it's addressing.

Here you go

Is that outdated there as well?

Yes. In fact you should not even use libunity any more, as it's outdated. You should rather emit the DBus signal directly, but that's another Issue.

Any news on this?

Release Notes Persisted

Don't check for Desktop Environment in setProgressBar and setBadgeCount.