Timeline for Design REST Polymorphic API
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2022 at 10:56 | answer | added | Cormac Mulhall | timeline score: 0 | |
| Jun 1, 2022 at 7:27 | answer | added | Robert Bräutigam | timeline score: 1 | |
| Jun 1, 2022 at 2:40 | answer | added | VoiceOfUnreason | timeline score: 1 | |
| May 31, 2022 at 21:38 | answer | added | Ewan | timeline score: 0 | |
| May 31, 2022 at 21:35 | comment | added | Carmine Ingaldi | @Ewan two main problems I've detected are: "how to restfully handle the case where a TYPE_3 is added and the client doesn't know how to process it?" and "how the client can apply the correct processing logic if a breaking change is introduced in contextual data for a certain activity type?" | |
| May 31, 2022 at 21:28 | comment | added | Ewan | is it really a problem if you include the type? why is that different from expecting the clients to be able to interpret a single type per end point? | |
| May 31, 2022 at 21:06 | history | asked | Carmine Ingaldi | CC BY-SA 4.0 |