Timeline for Is repeating an identifier on an API request and response considered a code smell
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2016 at 17:02 | history | edited | Bradley Thomas | CC BY-SA 3.0 |
deleted 12 characters in body
|
| Nov 8, 2016 at 16:53 | vote | accept | SurrealSyntax | ||
| Nov 8, 2016 at 16:52 | comment | added | SurrealSyntax | "If they have an ID, they are less dependent on their operational context. This means they are less tightly coupled, which is generally good practice." - that is what I was looking for. Thank you so much! | |
| Nov 8, 2016 at 16:47 | comment | added | Bradley Thomas | I have edited my answer to address your comment. | |
| Nov 8, 2016 at 16:47 | history | edited | Bradley Thomas | CC BY-SA 3.0 |
added 535 characters in body
|
| Nov 8, 2016 at 16:41 | comment | added | SurrealSyntax | The only thing is that it is not asking about everything for record X it is just saying give some things about record X - specifically record X's occurrence in the database (which is a calculated value). Do you still think it is good practice? Thank you for your time and answer! | |
| Nov 8, 2016 at 16:36 | history | answered | Bradley Thomas | CC BY-SA 3.0 |