ChrisTitusTech / ChrisTitusTech/warframe-linux

I01: P2: inventory import and sets

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

Nobody has claimed this yet.

enhancement phase:P2
Dominant language
Go
Stars
4
Forks
1
Avg merge
7m
Merged PRs (30d)
4

Description

Go implementation tracking epic

Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.

Child tasks

  • I01a: Validated inventory snapshot importer
    • Merged prerequisites: C02a.
    • Acceptance: R4: bounded schema-validated import; quantity/rank and unknown IDs preserved; malformed/duplicate input tests and atomic replacement.
  • I01b: Inventory table and corrections
    • Merged prerequisites: I01a, C02d.
    • Acceptance: R4/R8: quantity/rank/provenance, sort/filter and manual correction overlay separate from imported truth; empty/error and keyboard workflow demonstrated.
  • I01c: Set completion calculations and view
    • Merged prerequisites: I01b.
    • Acceptance: R4: set recipes plus owned quantities give correct gaps for hand-calculated fixtures; unknown coverage visible; no mastery inference.
  • I01d: Personal data export and deletion
    • Merged prerequisites: I01a.
    • Acceptance: R6: explicit export; delete snapshots/corrections/history with confirmation and transaction; fixtures and manual verification of remaining public catalog/cache.

Workflow

See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.

All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.

Contributor guide

Open the contributing guide

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.

Research direction

Start with TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then review the prerequisite order for C02a, C02d, and the four I01 child tasks. Treat I01a through I01d as separate PRs; completion requires their stated malformed-input tests, fixtures, manual checks, and updated task evidence, rather than implementing this epic in one change.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react, sqlite, typescript
Domain
database, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.