Process forms in chunks or use pagination
Open
A pull request for this has already been merged.
- #2710 by @Koc — merged
2. developing
enhancement
overview
- Dominant language
- JavaScript
- Stars
- 382
- Forks
- 127
- Avg merge
- 19h 31m
- Merged PRs (30d)
- 75
Description
This is more of a meta issue.
Currently for a lot of operations we query all (forms, submissions...) but for large instances this might get a problem if there are e.g. 30'000 forms or 3'000 submissions.
We should figure out a good way to handle:
- Show form results (fetching the results might be bad if there are hundreds or thousands of submissions)
- Investigate if there are more places that are problematic
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. Begin by locating the operations that fetch all forms or submissions and the code that displays form results. Done means defining and implementing an approach for large result sets, then investigating and documenting any other problematic unpaginated operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100