Enhancement: Alert history table (spec 7.5, AT-12)

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, database

Research direction

Start by reading the schema and account_settings code to see how entities are stored and found, then check spec 7.5 and the discussion in PR #17 for the alert event, device or scan, recipient, and timestamp fields. Add the alert_history table and entity class, implement store and find support, and add tests showing alerts can be recorded and retrieved. Done when the tests cover the required fields and behavior.

Written by the indexing model from the issue text.

Description

backend database Low Priority

The schema has no table recording alerts that were sent. It's needed for spec 7.5 "don't repeat an alert" (AT-12).

  • Add an alert_history table (which alert event, for which device/scan, sent to whom, when)
  • Entity class + store/find in account_settings
  • Tests

Milestone: M6. Raised in #17's PR.

Dominant language
Python
Stars
1
Forks
1
Avg merge
9h 31m
Merged PRs (30d)
36

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Bearkat-Professionals/Software-Engineering-Project

All issues in Bearkat-Professionals/Software-Engineering-Project

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.