inherited_resources 1.0.0 → 1.0.1

data/README.rdoc

@@ -257,6 +257,21 @@ give a block that expects two arguments, the first will be executed only in
 success scenarios and the second in failure scenarios. You keep everything
 clean and organized inside the same action.
 
+== Success and failure scenarios on destroy
+
+The destroy action can also fail, this usually happens when you have a
+before_destroy callback in your model which returns false. However, in
+order to tell InheritedResources that it really failed, you need to add
+errors to your model. So your before_destroy callback on the model should
+be something like this:
+
+    def before_destroy
+      if cant_be_destroyed?
+        errors.add(:base, "not allowed")
+        false
+      end
+    end
+
 == Some DSL
 
 For those DSL lovers, InheritedResources won't leave you alone. You can overwrite

data/lib/inherited_resources/base.rb

@@ -22,6 +22,7 @@ module InheritedResources
 
         # Add at least :html mime type
         respond_to :html
+        self.responder = InheritedResources::Responder
 
         helper_method :collection_url, :collection_path, :resource_url, :resource_path,
                       :new_resource_url, :new_resource_path, :edit_resource_url, :edit_resource_path,
@@ -39,6 +40,5 @@ module InheritedResources
     end
 
     inherit_resources(self)
-    self.responder = InheritedResources::Responder
   end
 end

data/lib/inherited_resources/version.rb

@@ -1,3 +1,3 @@
 module InheritedResources
-  VERSION = '1.0.0'.freeze
+  VERSION = '1.0.1'.freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: inherited_resources
 version: !ruby/object:Gem::Version 
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors: 
 - "Jos\xC3\xA9 Valim"
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-12-23 00:00:00 +01:00
+date: 2009-12-29 00:00:00 +01:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency