You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the GraphQL types are basically a verbatim implementation of the InterMine types. This means certain types contain fields that are mutually exclusive. For example, the Trait type can have a value for its qtlStudy field or its gwas field, but not both. The canonical way to handle this in GraphQL is to use a single field with a union or interface as its type. This will make the semantics of our GraphQL API more obvious and simplify client code that uses these types while enabling canonical functionality, e.g. filtering queries/results by type.
<edit>
Commit 24e8445 adds the necessary resolver support. </edit>
The following types should be updated to use this approach:
Location: chromsome/supercontig -> locatedOn
Trait: qtlStudy/gwas -> study; remove qlts and gwasResults since they can be accessed via study
DataSet: bioEntities; already generalized to type [BioEntity!]! but not implemented correctly
SequenceFeature:
childFeatures and overlappingFeatures; both fields are already generalized to type [SequenceFeature!]! but are not implemented correctly
chromsomeLocation/supercontigLocation -> location
chromsome and supercontig can be removed because they will be accessible via location.locatedOn
ExpressionValue: feature; already generalized to type SequenceFeature but not implemented correctly
PanGeneSets: transcripts; already generalized to type [Transcript!]! but not implemented correctly
The text was updated successfully, but these errors were encountered:
Currently the GraphQL types are basically a verbatim implementation of the InterMine types. This means certain types contain fields that are mutually exclusive. For example, the
Trait
type can have a value for itsqtlStudy
field or itsgwas
field, but not both. The canonical way to handle this in GraphQL is to use a single field with a union or interface as its type. This will make the semantics of our GraphQL API more obvious and simplify client code that uses these types while enabling canonical functionality, e.g. filtering queries/results by type.<edit>
Commit 24e8445 adds the necessary resolver support.
</edit>
The following types should be updated to use this approach:
chromsome
/supercontig
->locatedOn
qtlStudy
/gwas
->study
; removeqlts
andgwasResults
since they can be accessed viastudy
bioEntities
; already generalized to type[BioEntity!]!
but not implemented correctlychildFeatures
andoverlappingFeatures
; both fields are already generalized to type[SequenceFeature!]!
but are not implemented correctlychromsomeLocation
/supercontigLocation
->location
chromsome
andsupercontig
can be removed because they will be accessible vialocation.locatedOn
feature
; already generalized to typeSequenceFeature
but not implemented correctlytranscripts
; already generalized to type[Transcript!]!
but not implemented correctlyThe text was updated successfully, but these errors were encountered: