No delete endpoint for cards #5

New Issue

kalipso · 2026-06-22T11:35:20+02:00

kalipso commented

2026-06-22 11:35:20 +02:00

The generated openapi spec do not provide a delete endpoint for cards. Instead there is some GET endpoint /cards/delete. Through the specs it is not clear what this endpoint is doing, or what arguments it needs.

Please provide a DELETE endpoint /cards/{card_id}, consider removing the other one if there is no special need for it.

The generated openapi spec do not provide a delete endpoint for cards. Instead there is some GET endpoint `/cards/delete`. Through the specs it is not clear what this endpoint is doing, or what arguments it needs. Please provide a DELETE endpoint `/cards/{card_id}`, consider removing the other one if there is no special need for it.

ahtlon was assigned by kalipso

2026-06-22 14:53:01 +02:00

kalipso commented

2026-06-23 17:33:50 +02:00

To be able to identify which card should be deleted/deactivated we need some form of identifier within the model. Adding a field "Name" of type string should be sufficient.
This value must be provided during creation within the body of the post request.

To be able to identify which card should be deleted/deactivated we need some form of identifier within the model. Adding a field "Name" of type string should be sufficient. This value must be provided during creation within the body of the post request.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: malobeo/gatekeeper#5