It's now possible to serve :html, :xml, :json, :yml and :csv out of the box. Additional content types are handled equally easily by registering their symbols and then following simple naming conventions. The current README kind of reflects this, but it needs further explanation. Along with this to work correctly for displaying datamapper validation error collections, I filed a patch to the datamapper lighthouse which can be found at http://tinyurl.com/4czxm7
instance variables in nested resources should now really be initialized to the values one would expect them to have. Restructured specs to work like a standalone merb app. This means that the app can now be started via merb -i and also simply merb. As a consequence of this, specs can't be run via 'rake spec' from merb_resource_controller directory, but with 'rake spec' from inside the merb_resource_controller/spec/mrc_test_app directory. However, there are still a few request specs (and view matchers) I want to write to test nested resources even more comprehensively. The next step will be to incorporate nullobject's patch to allow xml and json responses. When this is done, I want to start thinking about how to *really* handle
The previous version only supported "leaf" models that are nested inside modules. With this commit it is now possible to use models that are nested inside modules all the way down the nesting strategy. So, on a "/articles/1/comments/1/ratings/1" route, you will be able to use classes Article, Community::Comment and Community::Rating (previously only Community::Rating was supported).
Also, the test app under spec/integration can now be booted with merb -i which makes playing around nicer.