Open axelstudios opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug The vast majority of our
POST
API endpoints show 201 (Created) as the http response code, when in reality it's almost always 200Expected Behavior The API documentation should accurately reflect the endpoints
Actual Behavior The API documentation is incorrect
Steps to Reproduce Compare the response codes shown in Swagger to the actual response codes, particularly with
POST
requestsAdditional Context If
@swagger_auto_schema
is not givenresponses
, it automatically assumesDELETE
returns 204,POST
returns 201, and everything else returns200
.