-
I've played a bit with the reek configuration and noticed it does not support config inheritance.
We've several projects, which have almost the same reek configuration with some exceptions/customizat…
-
Hi, Spencer!
I just assembly and welded the project during that last week. With the arduino routine compile in the arduino nano, I started to make the tests in the main PCB. Unfortunatelly, at the…
-
Hi! I used the Lint tool for analyze code. The result was: 249 items! The most important are:
1) There are 35 items with hardcoded texts, (because nobody defines the strings in string.xml file).
…
-
I found many materials describing bad smell in code, and I choose some which may be easy to check.
*Duplicated code
1. Same code structure in more than one place.
2. Same expression in two sibling su…
-
We have NilCheck, but we should detect more type checking, e.g.:
``` ruby
if foo.respond_to? :bar
foo.bar
end
```
``` ruby
case foo
when Bar
foo.bar
else
puts 'no bar!'
end
```
-
This is something I've been thinking about for some time.
There have been quite a few long-standing issues in the tracker that are not about Reek's core functionality. These have to do with configu…
-
It would be awesome to have integration with build tools such as the ones mentioned, which could then be parameterized to even fail the build in case of too many test smells, occurrence of some specif…
-
Extracted from #1026.
-
```
As a Developer, I want Code Smell detectors,
So that, Code Quality and Consistency can be maintained throughout the codebase.
```
-
1. delayed delivery
2. High variance on user activity (remember to exclude the instructor and TA)
3. Leader detector, most issues are created by the same user?
4. distribution of commits weekly, month…