From c05d8ed9cdcde9595257d00fd98c6f61b2680bde Mon Sep 17 00:00:00 2001 From: Jonathan Hefner Date: Wed, 29 Nov 2023 12:27:11 -0600 Subject: [PATCH] Link methods for Rails::Engine [ci-skip] --- railties/lib/rails/engine.rb | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/railties/lib/rails/engine.rb b/railties/lib/rails/engine.rb index bd01510d67..2fde36f44b 100644 --- a/railties/lib/rails/engine.rb +++ b/railties/lib/rails/engine.rb @@ -15,7 +15,8 @@ module Rails # feature and application sharing. # # Any +Rails::Engine+ is also a Rails::Railtie, so the same - # methods (like rake_tasks and +generators+) and configuration + # methods (like {rake_tasks}[rdoc-ref:Rails::Railtie::rake_tasks] and + # {generators}[rdoc-ref:Rails::Railtie::generators]) and configuration # options that are available in railties can also be used in engines. # # == Creating an Engine @@ -116,7 +117,7 @@ module Rails # An engine can also be a Rack application. It can be useful if you have a Rack application that # you would like to provide with some of the +Engine+'s features. # - # To do that, use the +endpoint+ method: + # To do that, use the ::endpoint method: # # module MyEngine # class Engine < Rails::Engine @@ -197,7 +198,7 @@ module Rails # named routes from the application will be available to your engine's controllers as well. # # However, sometimes you want to isolate your engine from the application, especially if your engine - # has its own router. To do that, you simply need to call +isolate_namespace+. This method requires + # has its own router. To do that, you simply need to call ::isolate_namespace. This method requires # you to pass a module where all your controllers, helpers, and models should be nested to: # # module MyEngine