Building the resource URL for the request is done for you by calling resource() of the model you are creating the request with.
This can be overridden with custom() for GET requests and for() for POST/PUT/PATCH/DELETE requests.
Users of the library often don't realize that custom() was made to query records on, for example, /posts/latest which is a conceivable resource URL. It is not RESTful to save/delete records on endpoints such as this.
People should be made aware that for() needs to be used for saving/deleting records.
The library should output a console error if save() is called after custom().
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4