Lysate and LysateBatchLayout
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the LysateBatchLayout element has a reference to the lysate it produces. This results in multiple LysateBatchLayout elements being able to point to the same Lysate, which should not happen. The Lysate object should have the reference to the LysateBatchLayout that has generated it.
Remove lysate_batch reference in Lysate because it will be through the LysateBatchLayout.
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
Locate the Lysate and LysateBatchLayout model definitions and inspect any existing tests for their relationship. Done means the relationship is represented from Lysate to the generating LysateBatchLayout, the LysateBatchLayout no longer stores the lysate reference, and the one-to-one constraint is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100