read source from stdin
Reported by Kevin Rutherford | March 8th, 2009 @ 02:12 PM
From Ashley Moran, via email:
"Not sure I like the way you pass ruby source on the command line. Maybe a separate option would work, eg
% reek --ruby "def hello; puts 'hello'; end"
It's more unix-y to pass source via stdin, eg
% reek <<-ENDRUBY heredocd> def hello heredocd> puts "Hello" heredocd> end heredocd> ENDRUBY
Comments and changes to this ticket
-
Kevin Rutherford March 8th, 2009 @ 02:15 PM
I added the option to treat arguments as source so that tests were easy to write. But on reflection I do prefer the idea of reading from stdin when no files are specified.
(If files are specified, but they don't exist, that's a fatal error; Reek should not then read from stdin.)
-
Kevin Rutherford March 22nd, 2009 @ 01:58 PM
- State changed from “new” to “resolved”
(from [198d556de6bf4f26f9084900e812e209a799a106]) Reads source code from $stdin when no files specified [#25 state:resolved] http://github.com/kevinrutherfor...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Defects and feature requests for Reek, the Ruby code smell detector
People watching this ticket
Kevin Rutherford
Tags
Referenced by
-
25
read source from stdin
(from [198d556de6bf4f26f9084900e812e209a799a106]) Reads s...