concern
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3
- 2.1.0
- 2.2.1
- 2.3.8
- 3.0.0
- 3.0.9
- 3.1.0
- 3.2.1
- 3.2.8
- 3.2.13
- 4.0.2
- 4.1.8 (0)
- 4.2.1 (0)
- 4.2.7 (0)
- 4.2.9 (0)
- 5.0.0.1 (0)
- 5.1.7 (0)
- 5.2.3 (0)
- 6.0.0 (0)
- 6.1.3.1
- 6.1.7.7
- 7.0.0
- 7.1.3.2
- 7.1.3.4
- What's this?
concern(name, callable = nil, &block)
public
Define a routing concern using a name.
Concerns may be defined inline, using a block, or handled by another object, by passing that object as the second parameter.
The concern object, if supplied, should respond to call, which will receive two parameters:
* The current mapper * A hash of options which the concern object may use
Options may also be used by concerns defined in a block by accepting a block parameter. So, using a block, you might do something as simple as limit the actions available on certain resources, passing standard resource options through the concern:
concern :commentable do |options| resources :comments, options end resources :posts, concerns: :commentable resources :archived_posts do # Don't allow comments on archived posts concerns :commentable, only: [:index, :show] end
Or, using a callable object, you might implement something more specific to your application, which would be out of place in your routes file.
# purchasable.rb class Purchasable def initialize(defaults = {}) @defaults = defaults end def call(mapper, options = {}) options = @defaults.merge(options) mapper.resources :purchases mapper.resources :receipts mapper.resources :returns if options[:returnable] end end # routes.rb concern :purchasable, Purchasable.new(returnable: true) resources :toys, concerns: :purchasable resources :electronics, concerns: :purchasable resources :pets do concerns :purchasable, returnable: false end
Any routing helpers can be used inside a concern. If using a callable, they’re accessible from the Mapper that’s passed to call.