README.md in restfulness-0.2.6 vs README.md in restfulness-0.3.0

- old
+ new

@@ -244,11 +244,11 @@ Resources also have support for simple set of built-in callbacks. These have similar objectives to the callbacks used in [Ruby Webmachine](https://github.com/seancribbs/webmachine-ruby) that control the flow of the application using HTTP events. The supported callbacks are: - * `exists?` - True by default, not called in create actions like POST. + * `exists?` - True by default, not called in create actions like POST or PUT. * `authorized?` - True by default, is the current user valid? * `allowed?` - True by default, does the current have access to the resource? * `last_modified` - The date of last update on the model, only called for GET and HEAD requests. Validated against the `If-Modified-Since` header. * `etag` - Unique identifier for the object, only called for GET and HEAD requests. Validated against the `If-None-Match` header. @@ -329,12 +329,12 @@ # More complex request path, from route: ['project', :project_id, 'task'] request.path.to_s # '/project/123456/task/234567' request.path # ['project', '123456', 'task', '234567'] request.path[:id] # '234567' -require.path[:project_id] # '123456' -require.path[2] # 'task' +request.path[:project_id] # '123456' +request.path[2] # 'task' # The request query request.query # {:page => 1} - Hash with indifferent access request.query[:page] # 1 @@ -615,9 +615,14 @@ * Support redirect exceptions. * Needs more functional testing. * Support for before and after filters in resources, although I'm slightly aprehensive about this. ## History + +### 0.3.0 - May 13, 2014 + + * Possible breaking change: `put` requests no longer check for existing resource via `exists?` callback. (@samlown) + * Avoid Rack Lint errors by not providing Content-Type or Length in empty responses. (@samlown) ### 0.2.6 - March 7, 2014 * Support scope block when adding a resource to router. (@samlown)