-
Notifications
You must be signed in to change notification settings - Fork 7
No dataFormat
arguments for sample/aminoAcidMutations
but sample/nuclotideMutations
Endpoint – inconsistent ?
#1159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
gordonkoehn opened this issue
Apr 22, 2025
· 2 comments
· Fixed by #1160, #1161 or loculus-project/loculus#4094
Closed
No dataFormat
arguments for sample/aminoAcidMutations
but sample/nuclotideMutations
Endpoint – inconsistent ?
#1159
gordonkoehn opened this issue
Apr 22, 2025
· 2 comments
· Fixed by #1160, #1161 or loculus-project/loculus#4094
Comments
sample/aminoAcidMutations
but sample/nuclotideMutations
Endpoint – inconsistent ?dataFormat
arguments for sample/aminoAcidMutations
but sample/nuclotideMutations
Endpoint – inconsistent ?
Thanks for finding this. It's indeed missing in the docs, but it should work correctly nonetheless. |
fengelniederhammer
added a commit
that referenced
this issue
Apr 22, 2025
…int in Swagger UI rseolves #1159
fengelniederhammer
added a commit
that referenced
this issue
Apr 22, 2025
…int in Swagger UI resolves #1159
1 task
fengelniederhammer
added a commit
that referenced
this issue
Apr 22, 2025
…int in Swagger UI resolves #1159
Hi Fabian, yes indeed it does work just fine. Blitz-patch indeed – Thanks. |
This was referenced Apr 22, 2025
This was referenced May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CovSpectrum API seems to have slightly differing arguments for the endpoints
sample/aminoAcidMutations
andsample/nuclotideMutations
.There is the argument
dataFormat
for the latter only. It is not obvious to me if this is by intend or accidental. At least is was suprising there was a difference to me when using.API Version: v2
Issue also consulted with @Taepper.
See the screenshots below:
The text was updated successfully, but these errors were encountered: