resource_controller: Redesign My API


  ## Before / After / Response

class PostsController < ResourceController::Base

  # block syntax
  create do
    before { @post.user = current_user }
    response do |wants|
      wants.html
      wants.js
    end
  end
  
  # chain syntax
  update.failure.wants.js
  
  # hybrid syntax
  update.failure do
    flash "There was a problem saving your object."
    wants.js
  end

end

## Alternate Model/Route/Object Naming

class PostsController < ResourceController::Base
  private
    def model_name
      'blog_post'
    end
    
    def route_name
      'article'
    end
end

## Alternate find syntax

class PostsController < ResourceController::Base
  private
    def object
      @object ||= end_of_association_chain.find_by_permalink(param)
    end
    
    def collection
      @collection ||= end_of_association_chain.find(:all, :page => {:current => params[:page], :size => 10})
    end
end

## Specific Actions

class PostsController < ResourceController::Base
  actions :all, :except => :edit
end

## Possible Parents

class PostsController < ResourceController::Base
  belongs_to :user, :category
end
  Backstory on my blog: http://jamesgolick.com/2007/11/5/resource_controller-redesign-my-api-at-refactormycode-com
  2007-11-05T20:27:18+00:00
  137
  Ruby
  resource_controller-redesign-my-api
  4
  resource_controller: Redesign My API
  
  2009-08-21T20:37:51+00:00
  2
  
    
      ## Alternate Model/Route/Object Naming

class PostsController < ResourceController::Base
  model_name :blog_post
  route_name :article
end
      137
      First refactoring from my blog...
      2007-11-05T20:28:27+00:00
      743
      Ruby
      0
      0
      On resource_controller: Redesign My API
      2
      jamesgolick
      http://jamesgolick.com
    
    
      ## Before / After / Response

class PostsController < ApplicationController
  acts_as_resource_controller

  # block syntax
  create do
    before { @post.user = current_user }
    respond_to do |format|
      format.html
      format.js
    end
  end
  
  # chain syntax
  update.failure.respond_to %w(js html)
end

## Alternate find syntax

class PostsController < ResourceController::Base
  object_finder :find_by_permalink
  collection_finder { find :all, :page => {:current => params[:page], :size => 10} }
end

      137
      A couple of suggestions. I'm used to the default respond_to rather then wants. And I don't know if the *_finder macros are even possible, but would look like a true dsl
      2007-11-05T22:24:51+00:00
      745
      Ruby
      4
      1
      On resource_controller: Redesign My API
      1
      macournoyer
      http://macournoyer.com
    
    
      update.failure.responds_to %(js html)
      137
      I love those. The *_finder macros are definitely possible. I really like the acts_as_resource_controller too. Currently, that syntax is just resource_controller, which I'm not crazy about.

I agree with you about the respond_to, although, I think for open syntax it should be responds_to, just because it reads like english - update responds to js and html. OTOH, I don't see much of a problem with having all of these names as aliases, and so I think I'll probably do that.
      2007-11-05T22:42:49+00:00
      746
      Ruby
      0
      0
      On resource_controller: Redesign My API
      2
      jamesgolick
      http://jamesgolick.com
    
    
        create do
    before { @post.user = current_user }
    responds_to :html, :js do |format|
      format.gif { create_gif(@post) }
    end
  end
      137
      I prefer responds_to. Since we're on the topic, how about making the block optional?
      2007-11-06T01:02:40+00:00
      751
      Ruby
      0
      0
      On resource_controller: Redesign My API
      3
      danielharan
      http://danielharan.com/