This repository has been archived by the owner on Oct 28, 2022. It is now read-only.
Moving the FeaturePhenotypeAssociation class to a more generic PhenotypeAssociation #322
Conversation
This file contains 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
…ypeAssociation. The PhenotypeAssociation is now allowed to link to Individuals and Samples.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The PhenotypeAssociation is now allowed to link to Individuals and Samples.
This change was originally proposed in: #264 (comment)
This also changes the proposed behavior of how Phenotypes are listed for Individuals. Originally it was a simple array embedded in the Individual record. This patch removes that, and replaces it with the ability to link Phenotypes to Individuals using the PhenotypeAssociation structure.