我以为我会拿出一个漂亮的方式在Rails 3.x的宝石延伸的ApplicationController。
在我的创业板公司lib/my_namespace/my_controller.rb
,我有:
class MyNamespace::MyController < ApplicationController
before_filter :some_method
after_filter :another_method
def initialize
# getting classname of the subclass to use for lookup of the associated model, etc.
# and storing the model_class in an instance variable
# ...
end
# define :some_method, :another_method, etc.
# ...
private
attr_accessor :subclass_defined_during_initialize # etc.
# etc.
end
但加载宝石时, app/controllers/application_controller.rb
还没有加载,所以它失败:
/path/to/rvm/gemset/gems/activesupport-3.2.6/lib/active_support/dependencies.rb:251:
in `require': cannot load such file -- my_gem_name/application_controller (LoadError)
作为一种变通方法,我在宝石的定义了ApplicationController中lib/gem_namespace/application_controller.rb
为:
class ApplicationController < ActionController::Base
end
我认为即使我已经有定义它,它会在我的Rails 3重新定义应用程序的app/controllers/application_controller.rb
,使得该扩展应用两个控制器ApplicationController
和扩展控制器MyNamespace::MyController
将直接或间接地延伸所限定的ApplicationController中app/controllers/application_controller.rb
。
然而,我们注意到,在加载后的宝石,扩展控制器ApplicationController
无法访问定义的方法app/controllers/application_controller.rb
。 此外, ApplicationHelper
(app/helpers/application_helper.rb)
模块不再被其他辅助模块加载。
我怎样才能延长ApplicationController
控制器内我的创业板定义的目的before_filter
和after_filter
和使用initialize
访问类的名称,以确定相关模型的类,它可能然后存储和方法中使用?
更新2012年10:
以下是我想出了:
在lib/your_gem_name/railtie.rb
:
module YourGemsModuleName
class Railtie < Rails::Railtie
initializer "your_gem_name.action_controller" do
ActiveSupport.on_load(:action_controller) do
puts "Extending #{self} with YourGemsModuleName::Controller"
# ActionController::Base gets a method that allows controllers to include the new behavior
include YourGemsModuleName::Controller # ActiveSupport::Concern
end
end
end
和lib/your_gem_name/controller.rb
:
module YourGemsModuleName
module Controller
extend ActiveSupport::Concern
# note: don't specify included or ClassMethods if unused
included do
# anything you would want to do in every controller, for example: add a class attribute
class_attribute :class_attribute_available_on_every_controller, instance_writer: false
end
module ClassMethods
# notice: no self.method_name here, because this is being extended because ActiveSupport::Concern was extended
def make_this_controller_fantastic
before_filter :some_instance_method_available_on_every_controller # to be available on every controller
after_filter :another_instance_method_available_on_every_controller # to be available on every controller
include FantasticStuff
end
end
# instance methods to go on every controller go here
def some_instance_method_available_on_every_controller
puts "a method available on every controller!"
end
def another_instance_method_available_on_every_controller
puts "another method available on every controller!"
end
module FantasticStuff
extend ActiveSupport::Concern
# note: don't specify included or ClassMethods if unused
included do
class_attribute :class_attribute_only_available_on_fantastic_controllers, instance_writer: false
end
module ClassMethods
# class methods available only if make_this_controller_fantastic is specified in the controller
def some_fanastic_class_method
put "a fantastic class method!"
end
end
# instance methods available only if make_this_controller_fantastic is specified in the controller
def some_fantastic_instance_method
puts "a fantastic instance method!"
end
def another_fantastic_instance_method
puts "another fantastic instance method!"
end
end
end
end