-
Notifications
You must be signed in to change notification settings - Fork 72
Open
Labels
category: engineeringFor product engineering, architecture work, tech debt and so on.For product engineering, architecture work, tech debt and so on.cooldownThis issue is a task or technical debt that would be appropriate for cooldown work.This issue is a task or technical debt that would be appropriate for cooldown work.type: technical debtThis issue/PR represents/solves the technical debt of the project.This issue/PR represents/solves the technical debt of the project.
Description
Description
We recently had an issue (#10713) where we were using a GET
request instead of a POST
with an extremely long query body.
This issue covers auditing the codebase to make sure we are using best practices across our internal API calls to the client API.
Acceptance criteria
- We are using the appropriate
GET
/POST
/etc. - Our route definitions (e.g. validation/arguments passed) are accurate and follow good practices.
Metadata
Metadata
Assignees
Labels
category: engineeringFor product engineering, architecture work, tech debt and so on.For product engineering, architecture work, tech debt and so on.cooldownThis issue is a task or technical debt that would be appropriate for cooldown work.This issue is a task or technical debt that would be appropriate for cooldown work.type: technical debtThis issue/PR represents/solves the technical debt of the project.This issue/PR represents/solves the technical debt of the project.