Closed thibaudgg closed 8 years ago
@dhagerty9009 this linter is providing a non-string content on text
field.
It's still an issue for me on Atom 1.1, too bad.
Do you have an example file that triggers this @thibaudgg?
Nothing special, I just save some random ruby files and it happens every time.
It's a known issue. I apologize for leaving it unfixed - work and school plus wedding planning have left me with precious little free time. I'm hoping to get to the issue this weekend. The main thing currently is that I'm performing a regex on the unformatted output from the reek
command. I'd like to move the output to JSON, an option provided by Reek, which would make parsing errors trivial.
This should be fixed now that I merged in PR #13.
Awesome it works now with 2.0.2! @dhagerty9009 thanks :gift:!
I got this error with linter-reek 2.0.1 & linter 1.8.0, disabling linter-reek make it goes away.