# Best practise for overriding rails helpers

**URL:** <https://www.ruby-forum.com/t/best-practise-for-overriding-rails-helpers/186595>\
**Category:** Rails\
**Created:** [April 9, 2010, 11:42am UTC](https://www.ruby-forum.com/t/best-practise-for-overriding-rails-helpers/186595 "2010-04-09T11:42:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmaxvv](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/85f322/32.png) [@cmaxvv](https://www.ruby-forum.com/u/cmaxvv)\
**Post date:** [April 9, 2010, 11:42am UTC](https://www.ruby-forum.com/t/best-practise-for-overriding-rails-helpers/186595/1 "2010-04-09T11:42:35Z")

</div>

hey all. I just overrode rails’ ‘options\_for\_select’ helper to take a  
third argument in each subarray which is used as the title (ie tooltip)  
for each option tag. I’m wondering in cases like this if best practise  
is to just leave it in application\_helper (where it is now) or if it’s  
better to draw attention to it by putting it in lib and properly  
overriding the existing options\_for\_select, wrapping it in the full  
module structure, ie

module ActionView  
module Helpers  
module FormOptionsHelper  
#custom method here  
end  
end  
end

what would y’all do?  
thanks, max