Timeline for Designing a REST API with resource relationships?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 12:39 | comment | added | Laiv |
This is also quite explicit but could result in a huge URL and isn't nice and tidy. Oh dear, looking for aesthetics in URL? Have you ever seen Google's URLs?
|
|
| Jun 11, 2020 at 8:20 | history | protected | gnat | ||
| Jun 11, 2020 at 6:00 | history | tweeted | twitter.com/StackSoftEng/status/1270958956173721601 | ||
| Aug 28, 2018 at 8:17 | answer | added | Matteo Ugolotti | timeline score: 0 | |
| Aug 27, 2018 at 22:36 | comment | added | Andy | Are you typically / always going to be getting the team + player data? | |
| Aug 27, 2018 at 2:09 | answer | added | VoiceOfUnreason | timeline score: 7 | |
| Aug 26, 2018 at 22:52 | comment | added | Adam Thompson | @Christophe thanks, I modified it to the more general case of resource relationships in general. | |
| Aug 26, 2018 at 22:52 | history | edited | Adam Thompson | CC BY-SA 4.0 |
edited title
|
| Aug 26, 2018 at 21:51 | comment | added | Christophe | COuldn't your title be miselading ? Because if one player belongs only to one team, it's a one to many relation and not many to many. | |
| Aug 26, 2018 at 21:38 | answer | added | Kwebble | timeline score: 2 | |
| Aug 26, 2018 at 20:08 | history | asked | Adam Thompson | CC BY-SA 4.0 |