Have you ever write code on Ruby On Rails with this use cases?
- Initialize object which will contain result of the method (the resulting object)
- Change the resulting object with some operations and the last operation might be nil
- Retun the resulting object from the first step. You should do it because you have to return not result of last operation and object which you manipulated with, ie the resulting object
There are a lot of ‘the resulting object’ references. Don’t they?
If your answer is yes this post is especially for you.
#How to use clean up the code?
Assume that you have method like I have already written above:
The is a perfect method in Ruby On Rails - returning. According rdoc we can clean up our code like this:
or like this:
The result of method my_action will be modified array. It doesn’t matter which approach to use: first or second. Choose which one you would like. So this code looks a little bit better then repetitive code which was before.
But there is a one pitfall. Let’s try to use it like this:
You will wonder that it doesn’t work as code like in my_action! We have changed reference for local object orders. That’s why we will have unexpected result: self instead of scope object (assume we passed :service_type parameter for instance, ie we called method: Order.search(:service_type => ‘test’)). We can use method returning here, so right code should be this:
So the conclusion of this post is to use method returning if you have initialized one object and do some changes and then return it. But be attentive: If you change reference for returning object to new object you will have result with old one.
Attention! Method returning provided ONLY Ruby On Rails, but NOT Ruby!
WideFix and Ruby On Rails expertise
At WideFix, we take pride in our expertise and experience. You can trust that our solutions will not harm your business and will always keep your site running smoothly. You can rely on us to provide confident and effective solutions that meet your needs.