Commit graph

15 commits

Author SHA1 Message Date
Kumi ae97cfa30e
refactor: clean up unused imports and improve code quality
Removed unnecessary imports across various modules to streamline the application's dependencies and improve loading times. Specific changes include the removal of unused Django model and admin imports in several apps, simplifying view imports by eliminating unutilized components, and cleaning up static CSS for better maintainability. Corrections were made to conditional expressions for clearer logic. The removal of the django.test.TestCase import in test files reflects a shift towards a different testing strategy or the current lack of tests. Exception handling has been made more explicit to avoid catching unintended exceptions, paving the way for more robust error handling and logging in the future. Additionally, a new CSS file was added for frontend enhancements, indicating ongoing UI/UX improvements.

These changes collectively aim to make the codebase more maintainable and efficient, reducing clutter and focusing on used functionalities. It's a step towards optimizing the application's performance and ensuring a clean, manageable codebase for future development.
2024-06-02 20:27:02 +02:00
Kumi 202c619315
feat(migrations): Initialize database schema for messaging
This commit introduces the initial set of database migrations required for setting up the foundational models of the messaging system within the application. These models include `GatewayUser`, `GatewayUserSetting`, `Notification`, and various scheduling entities to manage notification delivery timings. It lays the groundwork for linking users to their gateway preferences, storing customizable settings per gateway-user pair, and managing notifications with flexible scheduling options. This schema setup is crucial for supporting a dynamic and configurable messaging system, enabling efficient notification management and dispatching based on user preferences and predefined schedules.

By establishing a robust database schema upfront, we ensure that the application can scale effectively, facilitating ease of maintenance and future enhancements. This migration caters to the need for a cohesive and flexible data model to represent users, their notification preferences, and the logistics of notification dispatching and scheduling within the system.
2024-05-17 13:30:34 +02:00
Kumi a1164ad788 Remove dbsettings from init methods (would prevent initial migrations) 2021-03-01 07:09:53 +01:00
Kumi 84aaf34ec0 Fix matrix message delivery? 2021-02-20 14:17:52 +00:00
Kumi 788ae99088 Blindly code Matrix gateway 2021-02-17 06:43:24 +00:00
Kumi f9c52ce62b Fix notification sending for multiple dispatchers or no specified dispatchers 2021-01-15 15:14:08 +01:00
Kumi dee6be0b88 Send app specific data with Notification filter signal 2021-01-06 18:40:33 +01:00
Kumi 9d50530ca1 Send content of data field with Notification filter signal 2021-01-06 18:33:32 +01:00
Kumi e7c79578d4 Fix typo 2021-01-06 18:29:09 +01:00
Kumi 2cbd3960d7 Add field for additional (app specific) data to Notifications 2021-01-06 18:28:44 +01:00
Kumi 1f78158637 Implement filter signals for message processing 2021-01-02 10:13:07 +01:00
Kumi c25cac1ac2 Add management command to set Telegram token 2020-12-31 22:29:26 +01:00
Kumi 430ff93e45 Make message handler use local time instead of UTC 2020-12-31 22:15:52 +01:00
Kumi 3ae64b5caf Add django-dbsettings requirement
Move Telegram bot token to dbsettings (incl. migration)
2020-12-30 10:33:45 +01:00
Kumi 077c26bc0a Implement Telegram notifications
Some refactoring
2020-12-29 17:26:48 +01:00