-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Let the application know that a notification was closed #2471
Comments
Hi there, I would like to help with this issue if possible! |
This is currently not in the product backlog. Can this be assigned? @FabienLelaquais |
@FlorianJacta Certainly, yes. |
Could i help with this issue? |
Sure @Andre-Pestana0, I am assigning it to you |
Hello there, I have some doubts that I would like to share. First and foremost this is my work until now:
The final result can be seen by the following code and prints:
My questionI don't understand if the changes requested are these or if the reasons"forced" and "timout" should be something that the user never has to actually state |
Can you create a PR to explain what you have done like this message? Then, the R&D can discuss on it @Andre-Pestana0 |
Hello there @FlorianJacta, I have created the PR and put my doubt there as a comment |
Great, I have put as reviewers the R&D! @Andre-Pestana0 |
Description
We have no way to control whether a notification was closed or not.
It could make sense for the app to know about this, in order to potentially show other notifications that would be unreadable should too many notifications be visible yet.
Solution Proposed
Improve the notify() API with a callback:
notify(..., on_close=notification_closed)
and
def notification_closed(state, notification_id, reason
reason being "forced" or "timeout". I don't think we need to know whether the 'force' was manual or not.
Acceptance Criteria
Code of Conduct
The text was updated successfully, but these errors were encountered: