You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Rails 3.1 has view inheritance built in, it effectively renders this gem useless. The amount of time and effort to get all the issues sorted and tests added are too significant to warrant any more releases. If anyone is interested in taking over the project, please let me know! :)
Inherited Resources Views
Introduction
Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!
If you are confused about the difference to some other similarly named projects, please read on.
Difference to Inherit Views
Inherit Views adds the ability to render views from parent controllers. It does not share views between different resources.
Difference to Inherited Views
Inherited Views tries to solve the same problem we're solving, but from a slightly different angle. It is more complex, requires Formtastic and WillPaginate, and it only generates erb templates. Inherited Resources Views on the other hand, is extremely simple, is library-agnostic (it only depends on Inherited Resources), and it supports both erb and haml templates.