Timeline for REST Api Design Patterns
Current License: CC BY-SA 3.0
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2018 at 12:53 | history | tweeted | twitter.com/StackSoftEng/status/986588642566180864 | ||
| Apr 17, 2018 at 21:59 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 18, 2018 at 21:19 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 17, 2018 at 15:35 | review | Close votes | |||
| Feb 22, 2018 at 3:04 | |||||
| Feb 16, 2018 at 20:11 | answer | added | Laiv | timeline score: 1 | |
| Feb 16, 2018 at 16:43 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 17, 2018 at 15:47 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 18, 2017 at 15:32 | answer | added | Nicholas Shanks | timeline score: 0 | |
| Dec 5, 2017 at 10:10 | comment | added | Cormac Mulhall |
Can you explain what the filter is used for. It seems like you are using the filter for things that the URL should do. For example instead of of /api/users/:id/tasks?title:someValue why not do /api/users/:id/tasks/:title. Complex query strings are a headache, but as Laiv points out this isn't really anything to do with REST and more just to do with how you implement a system that takes an arbitrary amount of parameters and performs an action. Keep the query string as simple as possible and use URLs for everything else
|
|
| Nov 23, 2017 at 10:50 | history | asked | Lorenzo von Matterhorn | CC BY-SA 3.0 |