-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Change notification to be transient (notify-send) #11733
Conversation
Under GNOME Shell, using `--notify` (especially with `--watch`) floods the notification UI with unnecessary persistent copies of each notification that is raised. See jestjs#8773. This change uses [the `notify-send` `hint` option](https://www.npmjs.com/package/node-notifier#usage-notifysend) [`int:transient:1`](https://askubuntu.com/a/1185741) to make the notification transient.
Hi @BudgieInWA! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Thanks for the PR! @mikaelbr does this look correct? |
@mikaelbr would love a confirmation 🙏 |
This seems reasonable to me! Haven't been able to test it out on a UNIX box my self now (no immediate access), but from docs and examples, this makes sense. |
Great, thanks @mikaelbr! |
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.
thanks!
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Under GNOME Shell, using
--notify
(especially with--watch
) floods the notification UI with unnecessary persistent copies of each notification that is raised. This PR aims to close #8773.Test plan
I have only tested this under GNOME shell on Ubuntu. Run
jest --notify
orjest --watch --notify
and observe that the raised notifications are not added to the notification area.Judging by the use of the existing usage of the
actions
argument torequire('node-notifier').notify
, it is safe to pass this argument on all platforms, but I have not tested it.