Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add durable backing store behind `TaskStore`

Open
  • Is something wrong?
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python, sqlite
Domain
api, backend, cli, database

Research direction

Start by locating the current in-memory TaskStore and the API and CLI entry points that construct or use it. Compare the existing add, get, list, complete, and delete surface with a sqlite3-backed implementation, then verify that tasks survive process restart and that API and CLI behavior remains unchanged.

Written by the indexing model from the issue text.

Description

squad squad:backend

Scope: Introduce a durable storage backend (e.g., SQLite file-based store) implementing the same public surface as the current in-memory TaskStore (add, get, list, complete, delete). Keep the in-memory store available (e.g., as a default for tests) but wire a persistent implementation as the default runtime store used by API/CLI. Preserve constructor signature compatibility where practical; document any unavoidable break.

Acceptance criteria:

  • Tasks survive process restart when using the durable store.
  • TaskStore public method signatures unchanged (or documented deviations called out).
  • API and CLI work unmodified against the new store.

Notes: Prefer stdlib sqlite3 to avoid new dependencies unless the team decides otherwise.

Context:

  • Parent: #4
  • Size: M
  • Owner: Backend
  • Depends On: —

Part of the plan accepted for #4.
Related to #4

Generated by 🤖 Squad for #4 · copilot · auto · 54.9 AIC · ⌖ 26.1 AIC · ⊞ 19.7K · ◷
Comment /squad to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add bradygaster/squad/workflows/squad.md@bb5380b1ab5ceeb7d2ef3b3b0df4c364f9cada45
Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

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 bradygaster/squad-e4-validation

All issues in bradygaster/squad-e4-validation

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.