Closed emilymdubois closed 6 years ago
Add name to the item schema since id will now be an auto-generated integer
@emilymdubois if the id
is ever going to be user facing, for eg. in a URL, I'd strongly advocate for uuid
s and not auto incrementing integers. Happy to talk through.
@batpad yes, I think we could keep the auto_id
as the primary but masked ID, and then add an immutable field on a create operation that the user would use to in URL paths. PagerDuty always uses a 6-character string that always starts with P
.
We're going to use both POST and PUT operations, so we need to update how we create projects.
id
for URL queries, but assign an auto-generated ID on the backendPOST /projects/:project/items
endpointPUT /projects/:project/items/:item
endpoint to exclude creation eventsSimilar to tags, we'll want users to be able to pass an optional query parameter to filter projects by name instead of ID. Below, all instances of
:item
can be assumed to mean item ID, and all instances ofitem
can be assumed to mean item name.@batpad @kepta @samanpwbb
Get all project items
Query parameters
item
Create an item
Payload parameters
name
instructions
pin
status
open
.featureCollection
lock
Get an item
Update an item
Payload parameters
name
instructions
pin
status
open
.featureCollection
lock
Delete an item