OpenWISP Notifications 0.2.0
Not long ago, we released the 0.1.0 version of OpenWISP Notifications. While preparing the 0.1.0 release, we already started working on features for the next release. Similarly, we have already planned what to bring in the next version. Our goal is to bring new features to users as soon as we complete our rigorous testing. Without further wasting your time, let’s jump right into what version 0.2.0 has to offer.
Notable features of OpenWISP Notifications 0.2.0
- Snoozing notifications for a specific object
- Support for Django 3.1
- Improved accessibility
Snoozing notifications for a specific object
OpenWISP Notifications 0.1.0 aimed to provides users control over their notifications. With version 0.2.0, we are making that control more granular. OpenWISP Notifications 0.2.0 will allow users to selectively disable notifications for an object right from the admin site of that object
With the configuration of just one simple setting, the Ignore Notification Widget will be added to the admin webpage of a model. Through the widget, a user can snooze notifications of a specific object temporarily or permanently.
Support for Django 3.1
The 0.2.0 release brings official support of Django 3.1 to OpenWISP Notifications.
Accessibility Improvements
OpenWISP Notifications 0.1.0 brought a lot of features. We tried to ensure everything works as expected, but bugs are inevitable. Post releasing 0.1.0, we found out that at certain states, the notification widget could become inaccessible from the keyboard. While we fixed it right away, we wanted to ensure that it doesn’t break again and delayed it to version 0.2.0. All components introduced by OpenWISP Notifications are now more accessible. We are continuously working to make OpenWISP accessible by all.
The changes brought by OpenWISP Notification 0.2.0 are few but important. Don’t forget to check out the project’s documentation. Stay tuned for more features coming to OpenWISP.
Hang out with OpenWISP developers at our Gitter channel or send your queries and feature requests to our Mailing List.
