blocks|key|5204337|text|我最近开始为Ruby寻找这样的东西。到目前为止，我遇到的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5204338|5204339|Saikuro|unordered-list-item|offset|length|5204340|Roodi|5204341|Flog|5204342|5204343|这些可能是开始的地方。不幸的是，我还没有充分使用这三种方法中的任何一种来提供好的意见。|5204344|entityMap|0|LINK|mutability|MUTABLE|url|http://saikuro.rubyforge.org/|1|http://www.martyandrews.net/blog/2008/09/first_official_release_of_rood.html|2|http://ruby.sadi.st/Flog.html^0|0|0|0|7|0|0|0|5|1|0|0|4|2|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|12|8|@]|9|@$F|13|G|14|1|15]]|A|$]]|$1|H|3|I|5|E|7|16|8|@]|9|@$F|17|G|18|1|19]]|A|$]]|$1|J|3|K|5|E|7|1A|8|@]|9|@$F|1B|G|1C|1|1D]]|A|$]]|$1|L|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]|Y|$5|R|S|T|A|$U|Z]]]]

I've recently started looking for something like this for Ruby. What I've run across so far:

<ul>
<li><a href="http://saikuro.rubyforge.org/" rel="noreferrer">Saikuro</a></li>
<li><a href="http://www.martyandrews.net/blog/2008/09/first_official_release_of_rood.html" rel="noreferrer">Roodi</a></li>
<li><a href="http://ruby.sadi.st/Flog.html" rel="noreferrer">Flog</a></li>
</ul>

These might be places to start. Unfortunately I haven't used any of the three enough yet to offer a good opinion.

blocks|key|731578|text|Saikuro和Flog可以很好地了解代码复杂性的基本概念。您还可以使用像rcov这样的工具来查看您的测试覆盖率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|731579|有一个用于Rails项目的插件，可以将所有这些指标组合到一个rake任务中。它被称为metric_fu。|offset|length|731580|entityMap|0|LINK|mutability|MUTABLE|url|http://metric-fu.rubyforge.org/^0|0|16|9|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Saikuro and Flog can be good for getting a basic idea of code complexity. You can also use a tool like rcov to look at your test coverage. 
There is a plugin for Rails projects that combine all those metrics into a single rake task. It is called <a href="http://metric-fu.rubyforge.org/" rel="noreferrer">metric_fu</a>.

blocks|key|5204624|text|我最近找到并测试的项目：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5204625|5204626|https://github.com/railsbp/rails_best_practices+|unordered-list-item|offset|length|5204627|似乎起作用了，并提供了合理的warnings|5204628|5204629|5204630|​|5204631|5204632|https://github.com/simplabs/excellent+|5204633|工作正常，但有相当多的错误positives|5204634|5204635|5204636|5204637|5204638|https://github.com/troessner/reek我不同意这个工具的大部分警告，但it+works|5204639|+|5204640|5204641|5204642|5204643|5204644|http://www.cs.umd.edu/projects/PL/druby/+good|5204645|+|5204646|这需要ocaml；我还没有尝试过，但它看起来可能是ocaml|5204647|5204648|5204649|似乎不是Ruby1.9+compatible的|5204650|http://roodi.rubyforge.org/+|5204651|5204652|5204653|5204654|5204655|对于我来说，|5204656|https://github.com/gdb/ruby-static-checker+|5204657|已经坏了，它只捕获名称错误，所以单元测试应该覆盖that.|5204658|5204659|5204660|5204661|无法为me编译|5204662|https://github.com/michaeledgar/laser+|5204663|5204664|5204665|5204666|5204667|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/railsbp/rails_best_practices|1|https://github.com/simplabs/excellent|2|https://github.com/troessner/reek|3|http://www.cs.umd.edu/projects/PL/druby/|4|http://roodi.rubyforge.org/|5|https://github.com/gdb/ruby-static-checker|6|https://github.com/michaeledgar/laser^0|0|0|0|1B|0|1|1|0|0|0|0|0|11|1|1|1|0|0|0|0|0|X|2|0|0|0|0|0|0|0|14|3|0|0|0|0|0|0|0|R|4|1|1|0|0|0|0|0|16|5|1|1|0|0|0|0|0|11|6|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|2N|8|@]|9|@$F|2O|G|2P|1|2Q]]|A|$]]|$1|H|3|I|5|E|7|2R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2U|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]|$1|O|3|P|5|E|7|2W|8|@]|9|@$F|2X|G|2Y|1|2Z]]|A|$]]|$1|Q|3|R|5|E|7|30|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|31|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|U|3|M|5|6|7|33|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|W|3|X|5|E|7|35|8|@]|9|@$F|36|G|37|1|38]]|A|$]]|$1|Y|3|Z|5|6|7|39|8|@]|9|@]|A|$]]|$1|10|3|-4|5|E|7|3A|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|3B|8|@]|9|@]|A|$]]|$1|12|3|M|5|6|7|3C|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|3D|8|@]|9|@]|A|$]]|$1|14|3|15|5|E|7|3E|8|@]|9|@$F|3F|G|3G|1|3H]]|A|$]]|$1|16|3|17|5|6|7|3I|8|@]|9|@]|A|$]]|$1|18|3|19|5|E|7|3J|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1B|3|M|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|E|7|3N|8|@]|9|@$F|3O|G|3P|1|3Q]]|A|$]]|$1|1G|3|-4|5|E|7|3R|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1J|3|M|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|E|7|3W|8|@]|9|@$F|3X|G|3Y|1|3Z]]|A|$]]|$1|1O|3|1P|5|E|7|40|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|41|8|@]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|42|8|@]|9|@]|A|$]]|$1|1S|3|M|5|6|7|43|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|44|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|E|7|45|8|@]|9|@$F|46|G|47|1|48]]|A|$]]|$1|1X|3|-4|5|E|7|49|8|@]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]|$1|1Z|3|-4|5|6|7|4B|8|@]|9|@]|A|$]]|$1|20|3|M|5|6|7|4C|8|@]|9|@]|A|$]]|$1|21|3|-4|5|6|7|4D|8|@]|9|@]|A|$]]]|22|$23|$5|24|25|26|A|$27|28]]|29|$5|24|25|26|A|$27|2A]]|2B|$5|24|25|26|A|$27|2C]]|2D|$5|24|25|26|A|$27|2E]]|2F|$5|24|25|26|A|$27|2G]]|2H|$5|24|25|26|A|$27|2I]]|2J|$5|24|25|26|A|$27|2K]]]]

Projects I've found and tested recently:

<ul>
<li><a href="https://github.com/railsbp/rails_best_practices">https://github.com/railsbp/rails_best_practices</a>
<ul>
<li>Seems to work, and gives sensible warnings</li>
</ul></li>
<li><a href="https://github.com/simplabs/excellent">https://github.com/simplabs/excellent</a>
<ul>
<li>Works, but quite a few false positives</li>
</ul></li>
<li><a href="https://github.com/troessner/reek">https://github.com/troessner/reek</a>
<ul>
<li>I disagree with most of the warnings from this tool, but it works</li>
</ul></li>
<li><a href="http://www.cs.umd.edu/projects/PL/druby/">http://www.cs.umd.edu/projects/PL/druby/</a>
<ul>
<li>This requires ocaml; I haven't tried it, but it looks like it might be good</li>
</ul></li>
<li><a href="http://roodi.rubyforge.org/">http://roodi.rubyforge.org/</a>
<ul>
<li>does not appear to be Ruby 1.9 compatible</li>
</ul></li>
<li><a href="https://github.com/gdb/ruby-static-checker">https://github.com/gdb/ruby-static-checker</a>
<ul>
<li>Is broken for me, and only catches name errors, so unit tests should cover that.</li>
</ul></li>
<li><a href="https://github.com/michaeledgar/laser">https://github.com/michaeledgar/laser</a>
<ul>
<li>Doesn't compile for me</li>
</ul></li>
</ul>

blocks|key|2949481|text|你可能想试试RuboCop。它是一个基于Ruby+Style+Guide的Ruby代码风格检查器。它的维护相当活跃，并且基于标准的Ruby工具(如ripper库)。它可以很好地与Ruby+1.9和2.0协同工作，并且与Emacs进行了很好的集成。我希望你会发现它很有用！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2949482|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/bbatsov/rubocop|1^0|21|6|6|7|0|K|G|1|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@$9|R|A|S|1|T]|$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|M]]]]

You might want to try out <a href="https://github.com/bbatsov/rubocop" rel="noreferrer">RuboCop</a>. It is a Ruby code style checker based on the <a href="https://github.com/bbatsov/rubocop" rel="noreferrer">Ruby Style Guide</a>. It's maintained pretty actively and it's based on standard Ruby tooling (like the <code>ripper</code> library). It works well with Ruby 1.9 and 2.0 and has great Emacs integration. I hope you'll find it useful!

blocks|key|2948965|text|Dust看起来可以帮助你找到未使用的和无用的代码，这看起来有点符合你的需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2948966|我不知道还有其他类似的工具。|2948967|这个问题在ruby中比在java中要难得多--你会注意到所有那些java工具都标榜自己使用代码的静态分析。|2948968|ruby代码的静态分析通常是不可能的，因为没有任何静态的东西可以分析(方法通常是在运行时创建的，等等)|2948969|无论如何，其中一些东西在ruby中是不需要的，因为语言内置了它们。例如，您不需要一个编码标准来强制您的类都是NamedLikeThis的，因为如果它们不是，代码就不会工作。|style|CODE|2948970|另外，我必须补充一条标准免责声明，那就是那些工具通常会有点转移视线。你可以花一整天的时间让你的代码坚持工具认为它应该是什么样子，并最终得到比你开始时更多的错误。|2948971|我认为最好的解决方案是流利地编写代码，这样你就可以更容易地阅读它。任何数量的静态分析都不会像人类阅读代码那样好，因为它清楚地说明了它的意图。能够做到这一点是ruby比许多其他语言领先数光年的地方。我个人建议你努力学习如何更流利地编写，并教育你的团队关于这类事情，而不是把时间花在静态分析上。|2948972|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/kevinclark/dust/tree/master^0|0|4|0|0|0|0|0|1I|D|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|16|8|@$A|17|B|18|L|M]]|9|@]|C|$]]|$1|N|3|O|5|6|7|19|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1A|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]]]

<a href="http://github.com/kevinclark/dust/tree/master" rel="nofollow noreferrer">Dust</a> looks like it can help you find unused and useless code, which seems like it sort-of fits what you're after.

I'm not aware of any other such tools. 
This problem is vastly harder to address in ruby than it is in java - you'll note that all those java tools brand themselves as using 'static analysis' of the code. 
Static analysis of ruby code often isn't possible, because there isn't anything static that you can analyze (methods often get created at runtime and so on)

At any rate, some of these things are unneeded in ruby because the language builds them in.
For example, you don't need a coding standard to enforce that your classes are all <code>NamedLikeThis</code> because the code won't work if they aren't.

P.S. I have to add the standard disclaimer that those kind of tools can often be a bit of a red herring. You can spend all day making your code adhere to what the tool thinks it should be, and end up with more bugs than you started with. 
IMHO the best solution is to write your code fluently so you can read it more easily. No amount of static analysis is going to be as good as a human reading code which clearly states what it is meant to do. Being able to do this is where ruby is light-years ahead of many other languages. I personally would recommend you aim your efforts at learning how to write more fluently, and educating your team about such things, than spending time on static analysis.

blocks|key|731677|text|根据作者的说法，另一个很好的工具是恶臭：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|731678|http://reek.rubyforge.org/|offset|length|731679|reek目前包含了对以下代码气味的非常幼稚的检查：|731680|731681|Long+Method|unordered-list-item|731682|大类名称功能Envy|731683|Uncommunicative+Name|731684|长参数列表|731685|实用程序Function|731686|Nested+Iterators|731687|Control+Couple|731688|Duplication|731689|List项目|731690|731691|就我个人而言，我认为它仍然有太多的误报，但只要看看我的一些代码中的输出，就可以帮助我重新思考一些关于代码样式和架构的决定。|731692|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|Q|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1C|8|@]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|F|3|G|5|6|7|1G|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1I|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1J|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|1K|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1L|8|@]|9|@]|A|$]]|$1|R|3|S|5|K|7|1M|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|1N|8|@]|9|@]|A|$]]|$1|V|3|W|5|K|7|1O|8|@]|9|@]|A|$]]|$1|X|3|Y|5|K|7|1P|8|@]|9|@]|A|$]]|$1|Z|3|10|5|K|7|1Q|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1S|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|C]]]]

Another nice tool, although in early stages according to the author is reek:

<a href="http://reek.rubyforge.org/" rel="nofollow noreferrer">http://reek.rubyforge.org/</a>

reek currently includes very naive checks for the following code smells:

<ul>
<li>Long Method</li>
<li>Large Class</li>
<li>Feature Envy</li>
<li>Uncommunicative Name</li>
<li>Long Parameter List</li>
<li>Utility Function</li>
<li>Nested Iterators</li>
<li>Control Couple</li>
<li>Duplication</li>
<li>List item</li>
</ul>

Personally I think it still has too much false positives, but just looking at the output in some of my code helped me rethink some decisions about code style and architecture.

blocks|key|5204733|text|Code+Climate是一个通过git集成的SaaS工具，可以自动“评分”你的代码。如果质量突然下降，它会通过各种渠道通知您。用户界面也不错。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5204734|entityMap|0|LINK|mutability|MUTABLE|url|https://codeclimate.com/^0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="https://codeclimate.com/" rel="nofollow">Code Climate</a> is a SaaS tool that integrates through git and automatically "grades" your code. It notifies you via various channels if there a sudden drop in quality. Nice UI as well.

blocks|key|3793635|text|当我被问到这个问题时，我没有看到这个问题，但我写的一篇博客文章可能也会有所帮助。在这篇文章中，我介绍了一些Ruby工具，并特别介绍了4个代码质量工具……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3793636|3793637|Roodi|ordered-list-item|3793638|Dust|3793639|Flog|3793640|Saikuro|3793641|3793642|也许也值得去看看Towelie和Flay|3793643|http://devver.wordpress.com/2008/10/03/ruby-tools-roundup/|offset|length|3793644|现在，我们已经将许多工具组合到一个名为Caliper的Ruby代码质量和度量监控工具中。这可能很适合您的需求。它跟踪项目生命周期中的各种质量指标。|3793645|Caliper+-+improve+your+Ruby+code|3793646|entityMap|0|LINK|mutability|MUTABLE|url|1|http://getcaliper.com/^0|0|0|0|0|0|0|0|0|0|1M|0|0|0|0|W|1|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|1A|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1D|8|@]|9|@$Q|1E|R|1F|1|1G]]|A|$]]|$1|S|3|T|5|6|7|1H|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1I|8|@]|9|@$Q|1J|R|1K|1|1L]]|A|$]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|P]]|13|$5|Z|10|11|A|$12|14]]]]

I didn't see this questions when asked, but a blog post I did might help as well. In it I cover a bunch of Ruby tools and specifically cover 4 code quality tools...

<ol>
<li>Roodi</li>
<li>Dust</li>
<li>Flog</li>
<li>Saikuro</li>
</ol>

It might also be worth checking out Towelie and Flay

<a href="http://devver.wordpress.com/2008/10/03/ruby-tools-roundup/" rel="nofollow noreferrer">http://devver.wordpress.com/2008/10/03/ruby-tools-roundup/</a>

Now we have combined a lot of tools into an only Ruby code quality and metrics monitoring tool called Caliper. This might fit your needs well. It tracks various quality metrics over the life of a project.

<a href="http://getcaliper.com" rel="nofollow noreferrer">Caliper - improve your Ruby code</a>

blocks|key|727096|text|还有excellent。我还没有试过，但它看起来也很有前途。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|727097|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/simplabs/excellent^0|2|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There is also <a href="https://github.com/simplabs/excellent" rel="nofollow">excellent</a>. I haven't tried it yet, but it too looks promising.

One thing I really miss about Java is the tool support. FindBugs, Checkstyle and PMD made for a holy trinity of code quality metrics and automatic bug checking. 

Is there anything that will check for simple bugs and / or style violations of Ruby code? Bonus points if I can adapt it for frameworks such as Rails so that Rails idioms are adhered to.

Automatic code quality tool for Ruby?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

关于Java，我非常怀念的一件事就是对工具的支持。FindBugs、Checkstyle和PMD构成了代码质量度量和自动错误检查的三位一体。有没有什么方法可以检查Ruby代码的简单bug和/或风格冲突？如果我能把它改编成Rails之类的框架，以便遵循Rails的习惯用法，就会有额外的好处。

问Ruby的自动代码质量工具？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby的自动代码质量工具？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby的自动代码质量工具？
EN