This repository has been archived by the owner on Feb 22, 2023. It is now read-only.
[Feature] API code quality improvements #181
Labels
💻 aspect: code
Concerns the software code in the repository
🤖 aspect: dx
Concerns developers' experience with the codebase
🧰 goal: internal improvement
Improvement that benefits maintainers, not users
🟩 priority: low
Low priority and doesn't need to be rushed
🏁 status: ready for work
Ready for work
Problem
The API server can use some refactoring and code quality improvements in a lot of places for a smoother development experience. This is a task list to collect a bunch of ways to improve code quality in the Openverse API codebase.
APIView
.🚫 2. Documenting API responses dynamically generated using serializers for ensuring they stay up to date with the actual output. (Blocked as serializers need requests in the context)
'https://'
in some places which doesn't work for dev envsSerializerMethodField
s so that the correct data type is shown in the Swagger API docs.Additional context
Preferably make individual atomic PRs addressing one issue at a time, so that they can be reviewed and merged faster.
Implementation
The text was updated successfully, but these errors were encountered: