2 ms·

Your answer doesn’t explain why you made `capistrano-harrow` a dependency of `capistrano`. For example, RSpec 3.4 will use `coderay` for syntax highlighting [1

Your answer doesn’t explain why you made `capistrano-harrow` a dependency of `capistrano`. For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. That’s great! People who want syntax highlighting can install the extra gem and get the benefit; people who don’t care about syntax highlighting, or who don’t think it’s worth adding a dependency, can carry on as before. Why didn’t you do the same with `capistrano-harrow`? (I have no investment in the answer, just trying to clarify what others are asking about here.) [1] http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#install-coderay-for-syntax-highlighting http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#...

codebeaker 10y ago
> For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. Absolutely true, two observations: - I've often wondered about syntax highlighting in rspec to make things more readable in tests, I wish I would have known about this and seen it featured more prominently. - RSpec have no vested interest in promoting Coderay. I do have a vested interest in making Harrow come to break-even, if we don't make it break even I may have to step away from the FOSS work that I so enjoy. Thanks for sharing rspec+coderay, that's gonna make life in rspec projects much more bearable!