notification-persistence

Persist notifications in localStorage by initializing the notification service and calling its save method with notification data including id, taskId, message, timestamp, read status, and priority. The service stores up to 50 notifications and automatically removes older ones when the limit is exceeded.

Retrieve unread notifications by calling the getUnread method on the notification service, which filters stored notifications by read status. Use getAll to retrieve all persisted notifications, and count unread to track the total number of unread items.

Mark notifications as read using markAsRead or markAllAsRead methods. The service automatically removes notifications when associated tasks are deleted and enforces a 50-item retention limit, so old notifications are cleaned up without manual intervention.

Notifications stored in localStorage follow a defined schema with fields: id, taskId, message, timestamp, read status, and priority. This structure enables consistent CRUD operations across retrieval, filtering, and state management.

Yes, the notification persistence service integrates with task management workflows and notification UI components. It handles the storage layer while UI and task management handle display and triggering, allowing clean separation of concerns.