ossappscollective / ossappscollective/OSS-DocumentScanner

[FEATURE REQUEST] Document/card archive

Open
#644 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
2.4k
Forks
121
Avg merge
1d 58m
Merged PRs (30d)
17

Description

Is your feature request related to a problem? Please describe.
A type of cards that I frequently add to OSS card wallet is a gift card. These have limited usage (e.g. $30). When I see in the store that the card's balance is insufficient for my next purchase I currently would just delete that card (so that it doesn't Intermix with those that are still valid). However, sometimes the store would let me combine leftover balances of multiple cards for a new purchase. Thus, permanent card deletion does not really make sense in this case. Thus, I would currently still leave the card in the app and it would clutter the UI.

Describe the solution you'd like
I propose adding "card archive". A card can be archived (a bool flag) and unarchived. If a card is archived - it's not shown in the main app view. It is only accessible in the special "Archived cards" view.

Describe alternatives you've considered
I guess I could create a separate folder for archived cards, but the mental model is a bit different there

Additional context
Many other card wallet apps have archival feature so I though it might be interesting to people.

Contributor guide

No contributing guide indexed for this repository

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

The issue does not name files, tests, or entry points. Start by locating the card model and the main app view, then trace how cards are created, displayed, and deleted. Done means cards can be archived and unarchived, archived cards are hidden from the main view, and an Archived cards view exposes them.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.