Out-of-date Reek dependency breakage #3
Comments
jdickey
added a commit
to jdickey/crypt_ident
that referenced
this issue
Nov 27, 2018
This is a bare beginning; it turns out that three Guard tasks we'd really like to use are horriblly outdated and need to be forked/resuscitated; see * [this comment on periclesd/guard-flog#3](periclesd/guard-flog#3 (comment)) * periclesd/guard-flay#1 * periclesd/guard-reek#3 At least there's `guard-rake`. 🤓 44 tests, 63 assertions, 0 failures, 0 errors, 0 skips Coverage: 466 / 466 LOC (100.0%) covered. RuboCop: 7 files inspected, no offenses detected Flay: Total score 0 Flog: Total 161.3; method average 4.7; max 9.8 (CryptIdent::SignUp#create_result) Reek: 0 total warnings Inch: Nothing to suggest
This was referenced Nov 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I write this, the current version of Reek is 5.2.0, and this Gem's
.gemspecspecifies Reek 1.4.x).This puts this Gem in the same dusty attic as
guard-flogandguard-flay. As I mentioned in this comment on periclesd/guard-flog#3, I'd be very interested in helping resuscitate all three Gems.Anyone interested in helping move that effort forward, please give me a shout on Gitter. My work hours are beyond ridiculous, but I'd be happy to pitch in and at least help coordinate a reboot.
Thanks, everybody!
The text was updated successfully, but these errors were encountered: