Change API logic to handle multiple parents#52
Draft
HenryCrosswell wants to merge 33 commits into
Draft
Conversation
added 30 commits
June 11, 2026 09:14
…rk, refactored column renaming into own func
…rieve multiple responses
…s for what i am planning)
…ull mutations for all parent_sex once, adjusted other functions to fit
Merged with upstream main, to include pypi naming changes
…offspring line 163
…ions and docstrings
HenryCrosswell
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
What is this PR
Why is this PR needed?
Previous api pulls when multiple parents (1 male and 2 females) are involved would break the request
What does this PR do?
This pull request swaps hardcoded parents with dynamically numbered parents, so that any amount of parent data can be handled. Changes API request logic away from individual parents and combines them together as one request.
References
Progress towards issue #23
How has this PR been tested?
Yes, all tests pass with updated gin repo
Is this a breaking change?
Yes, as the standardisation changes are yet to be implemented, they will not currently work with the changes.
Does this PR require an update to the documentation?
Not yet
Checklist: