Log URL lifecycle
Open
bonus
- Dominant language
- Python
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We could keep in a separate table information about all actions performed on each given URL.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Review the Python Flask service and its SQLAlchemy data model first, then clarify which URL actions must be recorded and what the separate table should contain before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python, sqlalchemy
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100