RSpec
Ruby on Rails
Ruby
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3 (0)
- 2.1.0 (10)
- 2.2.1 (0)
- 2.3.8 (0)
- 3.0.0 (-2)
- 3.0.9 (-1)
- 3.1.0 (0)
- 3.2.1 (0)
- 3.2.8 (0)
- 3.2.13 (0)
- 4.0.2
- 4.1.8
- 4.2.1
- 4.2.7
- 4.2.9
- 5.0.0.1
- 5.1.7
- 5.2.3
- 6.0.0
- 6.1.3.1
- 6.1.7.7
- 7.0.0
- 7.1.3.2
- 7.1.3.4
- What's this?
-
all
-
global_plugins
-
inherited
-
new
-
<=>
(<= v2.3.8)
-
about
(<= v2.3.8)
-
app_paths
(<= v2.3.8)
-
classic_init_path
(<= v2.3.8)
-
config
-
controller_path
(<= v2.3.8)
-
engine?
(<= v2.3.8)
-
evaluate_init_rb
(<= v2.3.8)
-
gem_init_path
(<= v2.3.8)
-
has_app_directory?
(<= v2.3.8)
-
has_init_file?
(<= v2.3.8)
-
has_lib_directory?
(<= v2.3.8)
-
init_path
(<= v2.3.8)
-
lib_path
(<= v2.3.8)
-
load
(<= v2.3.8)
-
load_about_information
(<= v2.3.8)
-
load_deprecated_tasks
(<= v3.0.9)
-
loaded?
(<= v2.3.8)
-
load_paths
(<= v2.3.8)
-
load_tasks
(<= v3.0.9)
-
locale_files
(<= v2.3.8)
-
locale_path
(<= v2.3.8)
-
localized?
(<= v2.3.8)
-
metal_path
(<= v2.3.8)
-
railtie_name
-
report_nonexistant_or_empty...
(<= v2.3.8)
-
routed?
(<= v2.3.8)
-
routing_file
(<= v2.3.8)
-
valid?
(<= v2.3.8)
-
view_path
(<= v2.3.8)
= private
= protected
Rails::Plugin is nothing more than a Rails::Engine, but since it’s loaded too late in the boot process, it does not have the same configuration powers as a bare Rails::Engine.
Opposite to Rails::Railtie and Rails::Engine, you are not supposed to inherit from Rails::Plugin. Rails::Plugin is automatically configured to be an engine by simply placing inside vendor/plugins. Since this is done automatically, you actually cannot declare a Rails::Engine inside your Plugin, otherwise it would cause the same files to be loaded twice. This means that if you want to ship an Engine as gem it cannot be used as plugin and vice-versa.
Besides this conceptual difference, the only difference between Rails::Engine and Rails::Plugin is that plugins automatically load the file “init.rb” at the plugin root during the boot process.
