gqcpm / gqcpm/wavewatch

persistent data

Open
#8 0 comments 0 reactions 0 assignees View on GitHub
enhancement help wanted question refactor
Dominant language
Python
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

i would like to save persistent data rather than continually calling the api. This will help with speed and reduce api calling.

- [ ] ideal conditions for each point (longest term)
- [ ]

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Begin by locating where API calls are made and determining what data must persist and for how long. Done would require a defined persistence approach that reduces repeated API calls, but the issue does not specify storage, invalidation, or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.