That was one thought I had. That would be the easiest first pass at a gem that made the generators "compliant" - just make it add a rubocop config that allowed the default generated rails code to pass.
On Mon, Jul 18, 2016 at 6:16 AM, Greg Navis <cont...@gregnavis.com> wrote: > We can invert the problem and make rubocop support multiple styles. I > think this would be a better idea community-wide as it'd enable more > projects to use rubocop without having to reformat a significant part of > their code bases. > > I'm curious what you think. > > -- > 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. > -- 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.
