7254549dcd
In https://github.com/ruby/debug/issues/797, we found that requiring `debug` automatically activates it, which could introduce runtime overhead and cause memory bloat. And I think many users aren't aware of this and could be taxed by this unnecessarily (e.g. having longer builds on CI). Therefore, I propose to add `require: "debug/prelude"` after `debug`'s Gemfile entry in the default Gemfile template. This way, users can still use breakpoint methods like `debugger`, `binding.break`, and `binding.b`, but the debugger won't be activated until a breakpoint is hit. |
||
---|---|---|
.. | ||
bin | ||
exe | ||
lib | ||
test | ||
.gitignore | ||
CHANGELOG.md | ||
MIT-LICENSE | ||
railties.gemspec | ||
Rakefile | ||
RDOC_MAIN.md | ||
README.rdoc |
= Railties -- Gluing the Engine to the \Rails Railties is responsible for gluing all frameworks together. Overall, it: * handles the bootstrapping process for a \Rails application; * manages the +rails+ command line interface; * and provides the \Rails generators core. == Download The latest version of Railties can be installed with RubyGems: * gem install railties Source code can be downloaded as part of the \Rails project on GitHub * https://github.com/rails/rails/tree/main/railties == License Railties is released under the MIT license: * https://opensource.org/licenses/MIT == Support API documentation is at * https://api.rubyonrails.org Bug reports can be filed for the Ruby on \Rails project here: * https://github.com/rails/rails/issues Feature requests should be discussed on the rails-core mailing list here: * https://discuss.rubyonrails.org/c/rubyonrails-core