I have been looking around for something like checkstyle (Java code review tool) for ruby. http://checkstyle.sourceforge.net/availablechecks.html Has anyone here ever come across a similar dilema wherein we need to enforce the quality of ruby code written in different projects. What strategy could we adopt? Plan B would be to maybe use a web based code review tool with manual reviews, but thats really going back. cheers... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
The best code review tool is another person. Preferrably versed in the way of the Ruby. On Jan 17, 2008 3:33 PM, Jet <abhijatmahajan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I have been looking around for something like checkstyle (Java code > review tool) for ruby. > http://checkstyle.sourceforge.net/availablechecks.html > Has anyone here ever come across a similar dilema wherein we need to > enforce the quality of ruby code written in different projects. > What strategy could we adopt? > Plan B would be to maybe use a web based code review tool with manual > reviews, but thats really going back. > > cheers... > > > >-- Ryan Bigg http://www.frozenplague.net Feel free to add me to MSN and/or GTalk as this email. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Danny Challis
2010-Jul-13 16:19 UTC
Re: Looking for a Code review tool for ruby(checkstyle)
Hi Jet, This is the only one I could find, haven''t tried it yet, but it seems promising, if a bit young: http://github.com/martinjandrews/roodi/tree Jet wrote:> I have been looking around for something like checkstyle (Java code > review tool) for ruby. > http://checkstyle.sourceforge.net/availablechecks.html > Has anyone here ever come across a similar dilema wherein we need to > enforce the quality of ruby code written in different projects. > What strategy could we adopt? > Plan B would be to maybe use a web based code review tool with manual > reviews, but thats really going back. > > cheers...-- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Jul 13, 12:19 pm, Danny Challis <li...-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> Hi Jet, > This is the only one I could find, haven''t tried it yet, but it seems > promising, if a bit young: > > http://github.com/martinjandrews/roodi/treeMetric_fu includes roodi - it''s a decent place to start.> Jet wrote: > > I have been looking around for something like checkstyle (Java code > > review tool) for ruby. > >http://checkstyle.sourceforge.net/availablechecks.htmlI''ve personally found that (as Ryan suggested) the best "review" is a human reading the code. This is easier in Ruby than in Java, since there''s considerably less visual noise in a well-written block of Ruby. The metric_fu tools do identify several of the remaining issues (code duplication, excessive cyclomatic complexity,etc) but aren''t really intended to be used proscriptively (in other words, making a hard rule "no complexity ratings over 5 EVAR!" will lead to problems) but rather as a roadmap for detailed human review. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.