search for: make_resourceful

I am extremely proud to put the code up live for make_resourceful! I have been astonished by the positive feedback I''ve been receiving since our talk at this year''s RailsConf. So much pressure to get this thing out! If you haven''t heard about it... then check out my slides from railsconf http://www.hamptoncatlin.com/assets/2007/5/21/ma...

...a RESTful Rails application whose code and specs are becoming increasingly repetitive: every controller does pretty much the same set of things (give or take the occasional twiddle), for example, and so every controller spec is almost identical modulo some names, constants and strings. The make_resourceful plugin, which autogenerates the boilerplate REST actions, has gone a long way towards DRYing out the controller side of things, but I haven''t seen any examples of nice patterns for doing something similar on the spec side. I''m starting small here: I don''t even know...

I''ve just stumbled (literally, while I was trying to fix a glitch I was having after upgrading Aegis...) on the Inherited Resources gem... why did no-one tell me?! ;-) Is everyone else using some form of controller base-class? Am I the last on this bus! https://github.com/josevalim/inherited_resources -- You received this message because you are subscribed to the Google Groups

Hi, I''m really new to rails, so i programmed some stuff and today i read some things about skinny Controllers, fat models. My Controllers are really fat now. So i''m asking myself how can i shrink my controllers and move the code to the models, especially in fact of REST e.g. in focus on error codes? code example: # POST /tasks # POST /tasks.xml def create @authorized

Hi RSpec Mailing list, I''m new to RSpec and I am trying to get it running with the caboo.se sample rails app. I installed the current version of rspec with rspec_on_rails I tried to run rake spec but received: 330-07:~/desktop/restful_auth_rspec/vendor multimedia$ rake spec (in /Users/multimedia/Desktop/restful_auth_rspec)

Ez (or someone) asked on #merb tonight whether respond_to was the right API for what it does. After some discussion and pasties, I offer the following proposed API for content negotiation and response format selection: First, what does respond_to do right now? I see at as performing 3 distinct operations: 1. parse params[:format] and the accepts header to find out what format the

Is it just me or does anyone else miss being able to create something quickly. Once you start writing all the tests your time is now increased by a factor of 10. I agree with the logic in testing, but am I doing something wrong? Take the simple example of a controller test for an index action that shows all the forum posts for a user account. The controller code would be something like what is