-
```
It seems that in many cases, properties read from a JPEG 2000 image are used
for determining memory read/write addresses without first verifying that the
values are valid at all (such as image a…
-
Extracted from here: #328
---
Getting rid of the gazillions of constants for the parameter keys that are floating around in almost every smell detector and that used and spread across our spec suit…
-
Add a command-line option that disables all but the named smell. This should be a rake option too.
-
Noticed this when looking through different sites tonight.
https://www.gangbox.com/
When `ng-inspector` is _not_ installed, no exceptions are thrown in the console.
Once enabling `ng-inspector`, th…
-
```
It seems that in many cases, properties read from a JPEG 2000 image are used
for determining memory read/write addresses without first verifying that the
values are valid at all (such as image a…
-
```
It seems that in many cases, properties read from a JPEG 2000 image are used
for determining memory read/write addresses without first verifying that the
values are valid at all (such as image a…
-
```
It seems that in many cases, properties read from a JPEG 2000 image are used
for determining memory read/write addresses without first verifying that the
values are valid at all (such as image a…
-
```
It seems that in many cases, properties read from a JPEG 2000 image are used
for determining memory read/write addresses without first verifying that the
values are valid at all (such as image a…
-
I recently started trying to refactor SmellWarning and friends.
The thing that bothers me most about this class is the initializer:
``` Ruby
def initialize(class_name, context, lines, message,
…
-
I think we should lead by example and right now our example is failing big time with 129 total warnings reported on lib/..:)
How about we make reek absolutely smell-free?
We could also use this majo…