feat: Implement multi-user timetable tracking and notifications #1

Merged

Jannover5000r merged 3 commits from feature/multi-user-support into main

2025-10-10 23:00:28 +02:00

Jannover5000r commented

2025-10-10 12:18:50 +02:00

(Migrated from github.com)

Refactors the application to support multiple users for timetable logging.

User accounts added via a Discord command are now stored in accounts.json.
The main scheduling loop now fetches timetables for all registered users, in addition to the default user defined in the .env file.
Notifications for registered users are now sent as direct messages, providing personalized updates. The default user continues to use the existing webhook.
User-specific data files (e.g., timetable_filled_<userID>.json) are now used to keep each user's data separate.
Error handling has been improved to prevent the application from crashing if an operation fails for a single user.

Refactors the application to support multiple users for timetable logging. - User accounts added via a Discord command are now stored in `accounts.json`. - The main scheduling loop now fetches timetables for all registered users, in addition to the default user defined in the `.env` file. - Notifications for registered users are now sent as direct messages, providing personalized updates. The default user continues to use the existing webhook. - User-specific data files (e.g., `timetable_filled_<userID>.json`) are now used to keep each user's data separate. - Error handling has been improved to prevent the application from crashing if an operation fails for a single user.