Validation of huge (>10K samples) projects
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Project validation currently happens on the fly while updating (editing) the sample table/configuration.
For large projects, this causes small delays, making project editing less smooth and responsive.
One possible solution is to validate large projects on demand. For example, if a project contains more than 10K samples, the validation button would appear grayed out, indicating that the project has not yet been validated. Once the button is clicked, Pephub would run the validation process for that project.
Contributor guide
No contributing guide indexed for this repository
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 tracing project validation during sample table or configuration updates and locating the validation button and process. Define how projects over 10K samples are marked unvalidated and how explicit validation is triggered; done means editing remains responsive and the button clearly reflects validation state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100