-
Thing is, once you have 1) and 2), the added complexity of bringing in, integrating, and writing for a different tool to achieve 3) begins to make little sense, when you can just go along and do it just as well in rspec anyway... It's a matter of balance and heavily depends on the project.
> if you're still at Datadog
As a matter of fact I am. Feel free to shoot me an email.
curl -s https://github.com/DataDog/dd-trace-rb/commit/176c642ca73679cabc5fa1a113bc9b600aa04dcd.patch | grep '^From:' -
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
It mostly comes from the intentional design of open classes, thus the namespace organisation is fundamentally decoupled from the filesystem: any Ruby file has to be able to contain any class/module, otherwise one can't add to an open class/module†!
There are a bunch of issues about this upstream about this, e.g: https://bugs.ruby-lang.org/issues/14982
My take on it: https://github.com/lloeki/package-ruby
† ... via `class` and `module` keywords, as one could always include/extend/prepend or use `module_eval`/`class_eval`/`instance_eval`.
-
> debugger
Check out the latest IRB on 3.3, it finally gives Pry a run for its money!
https://github.com/ruby/irb#debugging-with-irb
$ ruby test.rb
