Timeline for REST API - Standard for also creating required parent entities?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2019 at 18:51 | comment | added | Roman Susi | @CormacMulhall Frameworks usually do have some preferred way for the API. It's not productive to fight too much against chosen framework. OP did not mention any frameworks, thus this small warning. | |
| Jun 5, 2019 at 17:04 | comment | added | Cormac Mulhall | @RomanSusi well yeah but you should be correctly encoding/decoding your URLs anyway. Many frameworks do that for you automatically, so it isn't that big a deal. | |
| Jun 5, 2019 at 15:55 | comment | added | Ant | This is the route we ended up going. Although I would usually agree with tom's approach mentioned below with limiting to one hop, what we're trying to accomplish is easier to maintain with only one endpoint with our name parameters. Another factor in deciding to go this route is that this is exclusively an internal call that will only be used by an integration from another app that we have. We've locked it down so that users won't be able to abuse it whether externally or internally. | |
| Jun 5, 2019 at 15:52 | vote | accept | Ant | ||
| Jun 5, 2019 at 14:56 | comment | added | Roman Susi | Including names in the URL can be a bit tricky and unsafe. For example, simple slash (/) in the name may require encoding name in URL-friendly way. | |
| Jun 4, 2019 at 16:15 | history | answered | Cormac Mulhall | CC BY-SA 4.0 |