bbatsov / rubocop / 4906

Builds Branch Commit Type Ran Committer Via Coverage
4906 master Don't warn for using eval() on a literal string Using eval on a string literal, with no computed values interpolated into it, is not a "security risk" and there is no need to warn about it. Why would anyone do this, anyways? Here is an example: ... Pull #2347 alexdowad travis-ci pending completion   set done
4905 master Don't warn for using eval() on a literal string Using eval on a string literal, with no computed values interpolated into it, is not a "security risk" and there is no need to warn about it. Why would anyone do this, anyways? Here is an example: ... Pull #2347 alexdowad travis-ci pending completion   set done
4904 master Don't warn for using eval() on a literal string Using eval on a string literal, with no computed values interpolated into it, is not a "security risk" and there is no need to warn about it. Why would anyone do this, anyways? Here is an example: ... Pull #2347 alexdowad travis-ci pending completion   set done
4903 master New braces_for_chaining style for BlockDelimiters. As per [the style-guide][style-guide], even though multi-line chaining is considered ugly and we should generally find ways to re-write the code, sometimes this simply isn't possible. Regardless,... Pull #2329 panthomakos travis-ci pending completion   set done
4902 master Don't warn for using eval() on a literal string Using eval on a string literal, with no computed values interpolated into it, is not a "security risk" and there is no need to warn about it. Why would anyone do this, anyways? Here is an example: ... Pull #2347 alexdowad travis-ci pending completion   set done
4901 master Don't warn for using eval() on a literal string Using eval on a string literal, with no computed values interpolated into it, is not a "security risk" and there is no need to warn about it. Why would anyone do this, anyways? Here is an example: ... Pull #2347 alexdowad travis-ci pending completion   set done
4900 master Merge pull request #2316 from maxjacobson/add-grammar-pluralization-cop Add Rails/PluralizationGrammar cop push bbatsov travis-ci pending completion   set done
4899 master Add Rails/PluralizationGrammar cop This cop makes sure that your code reads well when using the ActiveSupport methods for time duration. Bad: ``` 1.days.ago 3.week.from_now ``` Good: ``` 1.day.ago 3.weeks.from_now ``` Pull #2316 maxjacobson travis-ci pending completion   set done
4898 master Add Rails/PluralizationGrammar cop This cop makes sure that your code reads well when using the ActiveSupport methods for time duration. Bad: ``` 1.days.ago 3.week.from_now ``` Good: ``` 1.day.ago 3.weeks.from_now ``` Pull #2316 maxjacobson travis-ci pending completion   set done
4897 master Lint for ordinal circular argument references I noticed that Ruby emits a warning for ordinal circular argument references, not just optional keyword argument references. Should be helpful for RuboCop to lint for these as well. Pull #2346 maxjacobson travis-ci pending completion   set done
4896 master Bug: HashSyntax doesn't register offense with mixed keys. Pull #2345 dblock travis-ci pending completion   set done
4895 master Bug: parallel assignment with a side effect. Pull #2344 dblock travis-ci pending completion   set done
4894 master Bug: parallel assignment with a side effect. Pull #2344 dblock travis-ci pending completion   set done
4892 master Merge pull request #2333 from rrosenblum/count_with_arg [Fix #2331] Do not register an offense for count with an argument in Performance/Size push bbatsov travis-ci pending completion   set done
4891 master [Fix #2331] Do not register an offense for count with an argument in Performance/Size Pull #2333 rrosenblum travis-ci pending completion   set done