greptilian logo

IRC log for #rest, 2018-05-11

https://trygvis.io/rest-wiki/

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
01:23 Wildblue joined #rest
07:19 donofrio joined #rest
08:02 Haudegen joined #rest
12:34 interop_madness joined #rest
12:39 Haudegen joined #rest
13:20 saml ah i see. that makes sense
13:20 saml I'm also thinking about  POST /tasks/1:status    a separate endpoint used for updating status only. because PUT sounds like clients can modify all fields
13:21 saml and is HAL still relevant. or something better came?
13:24 mdk saml: I think there is currently no hypermedia type allowing to do clean REST (full hateoas, I mean to "discover" the different actions one can do on a resource, like POSTing a new one, or deleting one), typically HAL can't express that, it only can express "links" relations (GETs)
13:24 mdk saml: HTML is a good hypermedia type for this, but still no way to express DELETE or PUT in HTML so... at this point I don't know :]
13:26 mdk (anyway if you go for hal and want to change later, it's the role of HTTP to negociate the type so you'll be able to keep both)
13:26 mdk s/to negotiate/to allow the client to choose the type/
13:39 saml i compromise  :P
13:43 saml what's a good http status code if requested stuff isn't valid?  like  POST /tasks    task_type=yolo    but yolo is not a valid task type
13:43 saml 422?
13:49 mdk saml: I use a lot of 422 for this yep, still not sure it's ideal
14:54 saml what should be rel  of /tasks/1:status  ?
14:54 saml that link is used to update status of /tasks/1
17:09 Haudegen joined #rest
17:15 Haudegen joined #rest

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

https://trygvis.io/rest-wiki/