Timeline for Best practice for REST API call with many parameters
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2021 at 22:59 | answer | added | Purushotham CK | timeline score: 2 | |
| Sep 2, 2018 at 15:01 | history | tweeted | twitter.com/StackSoftEng/status/1036267803412783104 | ||
| Sep 2, 2018 at 11:47 | history | edited | Jose Alonso Monge | CC BY-SA 4.0 | Add more information |
| Sep 2, 2018 at 11:45 | comment | added | Jose Alonso Monge | 8 parameters is just an example. My Get operation is a "search" method. Think in an eCommerce scenario in which you want to search and filter "products" by name, description, category, brand, model, price, etc... I've edited the question to add context | |
| Aug 31, 2018 at 13:17 | comment | added | Filip Milovanović | Why do you have 8 parameters? What do they do? Is there some decision logic involved (and is it a mess)? Can you split that api/method into several methods that take 3 or 4 parameters? | |
| Aug 31, 2018 at 12:27 | comment | added | S.D. | Position is lesser of an identifier than a proper name for a value. | |
| Aug 31, 2018 at 11:57 | history | edited | sleske | CC BY-SA 4.0 | expand title; formatting |
| Aug 31, 2018 at 11:05 | answer | added | sleske | timeline score: 17 | |
| Aug 31, 2018 at 7:51 | answer | added | Ewan | timeline score: 8 | |
| Aug 31, 2018 at 7:40 | review | First posts | |||
| Sep 2, 2018 at 16:10 | |||||
| Aug 31, 2018 at 7:35 | history | asked | Jose Alonso Monge | CC BY-SA 4.0 |