On Wed, Jun 29, 2016 at 4:10 PM, Andrew Emelianenko < emelianenko....@gmail.com> wrote:
Hello! > > Current templates of scaffold controllers is little bit outdated. Not so > flexible and not very convenient. > I have written article about refactoring Rails Controllers: > http://rubywat.com/2016/06/26/how-to-cook-the-rails-controllers/ > > On my mind, it will be very useful for beginners if we will integrate this > in core of Rails. > > What do you think about this guys? > We definitely like the way controllers are idiomatically written today. An ivar is not bad per se, a filter is not bad per se. What you list as disadvanges are not categorically good or bad practices, their particular application in some problem or another may be. In Rails, controllers communicate with views using ivars, it's fine. Idiomatically they set the subject of some actions using filters to reuse the query. It's fine. Of course, it is also fine that your apps use your preferred style. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
