This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Improve beacon API specification coverage #35
Merged
Merged
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
cf037bc
to
9af24ed
Compare
b2cf830
to
fc22365
Compare
19a42d3
to
b0b28fb
Compare
43528ca
to
410ae15
Compare
410ae15
to
7a109a6
Compare
1000 Genomes container
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.
Improve beacon API specification coverage by addressing some of the misses identified such as:
CONTROLLED
is assuming the permissions are coming in the token and can be later addedAt the same time we introduce integration testing and server caching to improve performance:
info
endpoint was under-performing thus we added simple memory cache to it.Added:
variantType
key todatasetAlleleResponses
objectcounts
interpretation as pointed at Clarify the counts in Beacon response ga4gh-beacon/specification#237 (comment)