Improve Notifications API for common UX dismissal

[timheuer]

When using the Notifications API you can provide additional actions that render as buttons in the notification. There are times where the notification could be repeated, but the user may not want to see it anymore ("don't show again"). Currently, there is no common UX for that in the Notification API so each author is doing their own means and UX. Button text, location, resulting settings are not consistent for users.

Recommendation:

• Enable a simple optional parameter to show a common "Don't show again" affordance as a checkbox or other UX deemed appropriate.
• Ensure the API either in async/sync can get information whether that checkbox was checked or not to act upon it (store in their own settings, etc.). Since notifications can be transient, this shouldn't rely on any action being completed other than the checkbox/UX affordance itself.

[bpasero]

cc @daviddossett @isidorn

[vscodenpa]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[daviddossett]

Agreed—and it would be great to pair this effort, should we take it on, with the general notifications management proposal as shown here.

[vscodenpa]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscodenpa]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!