Hello Rails team, I'm not sure whether to post this question here or in the Rails core list. Please redirect me to the right forum if applicable.
Our team lead and I recently discussed the pros and cons of breaking up a long source file into multiple source files. I tend to prefer one class per file, because I find the individual files easier to read and easier to find (with ctrl-p in Sublime). On the other hand, our team lead doesn't have issues with long source files. He argues that they are quite common in open-source projects. As an example, he pointed to the ActionDispatch::Routing::Mapper <https://github.com/rails/rails/blob/e47e8e915e733177fe1dee2c67bef1724bbba553/actionpack/lib/action_dispatch/routing/mapper.rb> class in Rails as a case of a long file with multiple inline classes. I'm curious to learn the intent behind keeping all the contents of Mapper class within a single file. What were the advantages of taking this approach? Thanks, George Mendoza Philippines -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/e287edfe-2169-4e1e-8c56-957dd982434d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
