README.md in inherited_resources-1.5.0 vs README.md in inherited_resources-1.5.1

- old
+ new

@@ -1,5 +1,14 @@ +## Deprecation notice + +Since Rails 3 came out, I have no longer used Inherited Resources and it is no +longer actively maintained. I have found that the responders abstraction +offers the perfect balance between hiding and showing too much logic in controllers. +That said, I suggest developers to make use of Rails' `respond_with` feature +alongside the [responders gem](https://github.com/plataformatec/responders) as a +replacement to Inherited Resources. + ## Inherited Resources Inherited Resources speeds up development by making your controllers inherit all restful actions so you just have to focus on what is important. It makes your controllers more powerful and cleaner at the same time. @@ -206,11 +215,11 @@ ```ruby class ProjectsController < InheritedResources::Base protected def collection - @projects ||= end_of_association_chain.paginate(:page => params[:page]) + get_collection_ivar || set_collection_ivar(end_of_association_chain.paginate(:page => params[:page])) end end ``` The `end_of_association_chain` returns your resource after nesting all associations @@ -724,7 +733,6 @@ If you discover any bugs, please describe it in the issues tracker, including Rails and InheritedResources versions. Questions are better handled on StackOverflow. -Copyright (c) 2009-2012 José Valim http://blog.plataformatec.com.br -See the attached MIT License. +MIT License. Copyright (c) 2009-2012 José Valim.