I've intended the code for the view and I heard that it should be put into the helper if it's for the view. So, this is why I put it in helper.
How do you think about it?
I've stopped using Helpers. What would find was a method would be named with the intension it was used in a single view scope (e.g. within app/views/users), then as it was available everywhere it would be reused without making the method name more explicit.
Instead I've opted for either model decorators, or the collection_select helper e.g:
This is kind of a cool problem to solve!
What are your thoughts about moving your helper method onto the model?
Thanks!
I've intended the code for the view and I heard that it should be put into the helper if it's for the view. So, this is why I put it in helper.
How do you think about it?
I've stopped using Helpers. What would find was a method would be named with the intension it was used in a single view scope (e.g. within
app/views/users), then as it was available everywhere it would be reused without making the method name more explicit.Instead I've opted for either model decorators, or the
collection_selecthelper e.g:LGTM!! It's a better way. Thank you.