More options to make delegate more flexible
Reported by porras | September 20th, 2008 @ 12:56 PM | in 2.x
Adds two options to delegate to make it more flexible and support two frequent patterns in delegation.
You can specify a target if you don't want your method to have the same name:
class Foo < ActiveRecord::Base
belongs_to :greeter
delegate :hi, :to => :greeter, :target => :hello
end
Foo.new.hi # returns Foo.new.greeter.hello
If the object in which you delegate can be nil, you may want to use the :allow_nil option. In that case, it returns nil instead of raising a NoMethodError exception:
class Foo
def initialize(bar = nil)
@bar = bar
end
delegate :zoo, :to => :bar
end
Foo.new.zoo # raises NoMethodError exception (you called nil.zoo)
class Foo
def initialize(bar = nil)
@bar = bar
end
delegate :zoo, :to => :bar, :allow_nil => true
end
Foo.new.zoo # returns nil
Comments and changes to this ticket
-
Pratik September 24th, 2008 @ 11:21 PM
- → Title changed from [PATCH] More options to make delegate more flexible to More options to make delegate more flexible
-
porras September 24th, 2008 @ 11:23 PM
- → Title changed from More options to make delegate more flexible to [PATCH] More options to make delegate more flexible
This is almost a duplicate of http://rails.lighthouseapp.com/p...
I added the :allow_nil option to it.
-
porras September 24th, 2008 @ 11:25 PM
- → Title changed from [PATCH] More options to make delegate more flexible to More options to make delegate more flexible
Fixing unintentional change of title.
-
Daniel Schierbeck October 3rd, 2008 @ 03:57 PM
- → Tag changed from activesupport enhancement patch to activesupport duplicate enhancement
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
