Cache datasource ID while using datasource API
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 200
- Forks
- 30
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 35
Description
Currently they are refetched from db
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the datasource API entry point and the code that currently refetches datasource IDs from the database. Determine the intended cache scope and invalidation behavior, then add coverage showing that repeated datasource API use does not refetch the ID unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100