pgadmin-org / pgadmin-org/pgadmin4
Use URL based data caching using react-query instead of manual
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Currently, pgAdmin uses manual caching/busting for a lot of endpoint data. It also uses some kind of node based mechanism to store data.
While this works in most cases, it doesn't in few cases and is not easy to fix as well. Manual caching is also prone to error.
I suggest we should use URL based caching overall without getting into which node the cache should be on. Its noteworthy that we already have server group id, server id, db id, etc in our URL endpoints.
API querying and caching can be easily taken care by react-query for a more streamlined solution.
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
No files, tests, or entry points are named. Start by reading the linked react-query documentation and locating pgAdmin's existing manual caching, cache-busting, and node-based storage mechanisms; done would mean a defined URL-based caching approach replaces the current manual approach across the intended endpoint data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, react
- Domain
- backend-api-design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100