Swagger UI #805
Swagger UI #805
Conversation
Co-authored-by: Aurélien Luciani <[email protected]>
Co-authored-by: Daniel Rice <[email protected]>
src/help/utils/apiSnippets.tsx
Outdated
| return '# No automatic snippet, work in progress'; | ||
| } | ||
|
|
||
| return `# Perl not recommended, limited support |
There was a problem hiding this comment.
Are we trying to say that Perl in general is not recommended to access our API or just that the specific snippets may not work? I'm thinking in general we should be fully supporting perl (and R) or any other means of accessing our API as it's just making HTTP. What do you think?
There was a problem hiding this comment.
It's not really that we won't be giving support but rather to push people to use Python and to not expect support for Perl or R, first because in the team we don't really use this, and then to deter new bioinformaticians because in 2024 it might not be the best thing to learn first (especially Perl) unless they have a really good reason.
We could rephrase as "Limited support by the UniProt helpdesk in Perl" or something else that would not make it sound like we say the language itself is deprecated.
There was a problem hiding this comment.
Sounds good, maybe something like: "Note that there is limited UniProt help desk support for Perl-related questions."
Purpose
Swagger-UI first implementation
Approach
Testing
Yes
Checklist