Christopher DeCairos
Christopher DeCairos
This concerns me... project.id is a `bigserial` type (auto incrementing bigint), which shouldn't ever try to create a row with a duped project id...
I've yet to encounter this issue, can we backlog it?
cc/ @thisandagain
Here's mostly what this will be broken into: - test - services - api - handlers - bulk - index.js - docs - index.js - elements - getAllInPage.js - getOne.js...
we'll need to make sure we dont break the method caching and invalidation code
It's probably because OPTIONS requests are mainly generated by browsers, and don't modify anything. it'd just be unnecessary overhead for the server to validate
It does sound like we can/should modify the options requests to return 204 statuses instead of 200
That's a good point. The UA will inevitably try hitting the same route with GET/POST/PATCH etc and get the right status anyways.
relevant JSON API issue: #80
:+1: I think we also should look at making sure things properly cascade (I don't think they do right now!). i.e. a project delete also moves its child pages and...