CHANGELOG

The problem was that I had changed resource_saved?‘s behaviour to not saving the model if it had already been saved. In the future resource_saved? will be deprecated, but not yet.

BTW. All of these changes to resource_saved? behaviour is aimed at making RC drop in compatible with rspec‘s generated controller specs (try rake spec:generate).

To do that I need the default update action to use :update_attributes. This meant that the old strategy of keeping track of saves by using save_resource wont work. Instead, we keep track by looking at the AR‘s state (see lib/ardes/active_record/saved.rb) which is a far better solution anyway.

So save_resource is now deprecated, just use resource.save ActiveRecords can now be asked if they are saved?

 form_for_resource :url_options => {:gday => 'mate'}

 # => action="/products/1?gday=mate"  (for update)
 # => action="/products?gday=mate"    (for create)

This means you can connect a named route up with a REST action and also change the method

map.activate_account ’/activate/:code’, :controller => ‘activations’, :action => ‘create’, :resource_path => ’/activations’, :resource_method => :post

:erp retained for BC

response_for :create do |format|

  if resource_saved?
    format.html {}
  else
    format.html {}
  end

end

def create

  self.resource = new_resource
  save_resource

end

Use the :erp param when you are routing a non RESTful route to your rc controller This allows rc to load the resources using the route.

e.g. map.home ’’, :controller => ‘forums’, :action => ‘index’, :erp => ’/forums‘

This can be useful when you have a tree like domain:

  map.resources :categories do |category|
    category.resources :categories
  end

  class CategoriesController < ApplicationController
    resources_controller_for :categories
    map_resource :category, :as => :parent
  end

  resources_controller_for :forums, :only => [:index, :show]
  resources_controller_for :forums, :actions => MyActions, :except => :destroy

The method used to achieve this is Ardes::ResourcesController::include_actions which can be used in any ActionController when resources_controller is in your plugins directory

    resources_controller_for :tags
    nested_in :taggable, :polymorphic => true

  This will load the enclosing resource (which can be a mapped resource) as
  @taggable as well as its default name

  The following syntax is equivalent to the above two lines:
    resources_controller_for :tags, :in => '?taggable'

  And you can specify a single wildcard '?' as well as expanding wildcards '*':
    resources_controller_for :images, :in => '?', :load_enclosing => false
    # this will work for routes like /users/1/images, /forums/2/images, /featured/images

• test coverage is up
• moved some of the ‘friend’ functionality out of Specification, as it smelt bad

Fixed a bug where the resource mapping was using name instead of segment to match when a map should be used (this meant mapping didn‘t work for non singleton resources)

Thanks to Inviz <invi…@gmail.com> and Matt Mower <matt.mo…@gmail.com> in groups.google.com/group/resources_controller/browse_thread/thread/b71b2ce196a09d15 for the bug reports

  prepend_before_filter :load_enclosing_resources
  resources_controller_for :foos

(common case for the above is where superclass defines filters that need access to enclosing resources)

  admin.resources :forums

end

module Admin

  module Forums < ApplicationController
    resources_controller_for :forums
  end

end

in an action:

  resources_path # => '/admin/forums'
  enclosing_resources # => []

 - load_enclosing is now true by default
 - BC: the old options work for now, but you'll get deprecation messages
 - refactored a lot of code into friend classes - in particular there is now
   ResourcesController::Specification which specifies how to find a resource from the route

  class TagsController < ApplicationController
    resources_controller_for :tags, :load_enclosing => true
  end

  this will service all these routes (loading the resources into assigns for the view)

    /tags
    /forums/2/tags
    /images/1/tags
    /home/tags          <= singular resource
    /users/1/image/tags <= nested singular resource

  Also

  class BlogController < ApplicationController
    resources_controller_for :blog, :singleton => true, :load_enclosing => true
  end

  class PostController < ApplicationController
    resources_controller_for :post, :load_enclosing => true
  end

  for /campaigns/1/blog
      /users/2/blog
      /campaigns/1/blog/posts
      /users/2/blog/posts

      etc...

TODO: rewrite docs - for now check out the spec suite. TODO: refactor code - I did it BDD stylee, so there‘s lots of specs but also a lot of code that ‘is the simplest thing that makes the specs pass‘

Decided that Patching Routing was a bad idea, so route is re-recognized using the request path. This only happens for controllers with :load_enclosing => true

Example:

  class PostsController < ApplicationController
    resources_controller_for :posts
  end

  class UserPostsController < PostsController
    nested_in :user

    before_filter {|c| raise 'boom' if @user.name == 'Santa'}
  end

So to get the path to edit a child tag resource (where resource is ‘forum:1’)

  edit_resource_tag_path(@tag) # => '/forums/1/tags/2/edit'

  resource_path(:sort_by => 'article') # => '/forums/2?sort_by=article'