Timeline for REST API path parameter with multiple meanings
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2020 at 14:48 | vote | accept | Aurast | ||
| Oct 15, 2020 at 11:48 | comment | added | Laiv |
But I have a vague feeling that that may not be the best way to do it, because now the /projects/{id|"tags"} route has two different meanings. URIs are addressed to HTTP clients, who could not care less about meanings. If you are writing URIs for humans, then you have many more problems. More precisely one for every single human being allowed to read your API endpoints.
|
|
| Oct 15, 2020 at 0:19 | answer | added | VoiceOfUnreason | timeline score: 2 | |
| Oct 14, 2020 at 16:43 | answer | added | Dan Wilson | timeline score: 2 | |
| Oct 14, 2020 at 15:59 | answer | added | s.lg | timeline score: 1 | |
| Oct 14, 2020 at 15:40 | history | asked | Aurast | CC BY-SA 4.0 |