PEtab-dev / PEtab-dev/libpetab-python
v2 validation: atomize checks
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
#288 introduces a new validation frame work. so far, a lot of v1 code is reused, and many things are checked together. however, it would be preferable to have more fine-grained checks.
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 reading issue #288 and the validation framework it introduced, then compare the reused v1 validation code described here. Define the individual checks and their boundaries before changing the validation structure; done means the previously combined checks can be run and reported independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100