dry-auto_inject 0.6
dry-auto_inject 0.6
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/0.6/basic-usage/index.html.gz b/gems/dry-auto_inject/0.6/basic-usage/index.html.gz index 78528dd125..ee8f69f0b5 100644 Binary files a/gems/dry-auto_inject/0.6/basic-usage/index.html.gz and b/gems/dry-auto_inject/0.6/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/0.6/how-does-it-work/index.html b/gems/dry-auto_inject/0.6/how-does-it-work/index.html index a21277c5df..e83e545994 100644 --- a/gems/dry-auto_inject/0.6/how-does-it-work/index.html +++ b/gems/dry-auto_inject/0.6/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject 0.6
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject 0.6
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject 0.6
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject 0.6
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject 0.6
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject 0.6
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-auto_inject 0.7
dry-auto_inject 0.7
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/0.7/basic-usage/index.html.gz b/gems/dry-auto_inject/0.7/basic-usage/index.html.gz index 6e0668acc5..e3d3f89007 100644 Binary files a/gems/dry-auto_inject/0.7/basic-usage/index.html.gz and b/gems/dry-auto_inject/0.7/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/0.7/how-does-it-work/index.html b/gems/dry-auto_inject/0.7/how-does-it-work/index.html index 5845136aec..60d66d5eb3 100644 --- a/gems/dry-auto_inject/0.7/how-does-it-work/index.html +++ b/gems/dry-auto_inject/0.7/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject 0.7
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject 0.7
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject 0.7
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject 0.7
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject 0.7
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject 0.7
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-auto_inject 0.8
dry-auto_inject 0.8
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/0.8/basic-usage/index.html.gz b/gems/dry-auto_inject/0.8/basic-usage/index.html.gz index fa98d30e1f..1404c7f86a 100644 Binary files a/gems/dry-auto_inject/0.8/basic-usage/index.html.gz and b/gems/dry-auto_inject/0.8/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/0.8/how-does-it-work/index.html b/gems/dry-auto_inject/0.8/how-does-it-work/index.html index 3f62ccf837..13cc6a07b8 100644 --- a/gems/dry-auto_inject/0.8/how-does-it-work/index.html +++ b/gems/dry-auto_inject/0.8/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject 0.8
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject 0.8
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject 0.8
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject 0.8
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject 0.8
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject 0.8
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-auto_inject 0.9
dry-auto_inject 0.9
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/0.9/basic-usage/index.html.gz b/gems/dry-auto_inject/0.9/basic-usage/index.html.gz index 516e4e1f9c..bdb729ea97 100644 Binary files a/gems/dry-auto_inject/0.9/basic-usage/index.html.gz and b/gems/dry-auto_inject/0.9/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/0.9/how-does-it-work/index.html b/gems/dry-auto_inject/0.9/how-does-it-work/index.html index 16eccaeaf3..7b4ba45cb2 100644 --- a/gems/dry-auto_inject/0.9/how-does-it-work/index.html +++ b/gems/dry-auto_inject/0.9/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject 0.9
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject 0.9
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject 0.9
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject 0.9
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject 0.9
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject 0.9
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-auto_inject 1.0
dry-auto_inject 1.0
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/1.0/basic-usage/index.html.gz b/gems/dry-auto_inject/1.0/basic-usage/index.html.gz index 5d2365732a..5480bc3c0f 100644 Binary files a/gems/dry-auto_inject/1.0/basic-usage/index.html.gz and b/gems/dry-auto_inject/1.0/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/1.0/how-does-it-work/index.html b/gems/dry-auto_inject/1.0/how-does-it-work/index.html index 09825bcb41..0144d7c2d1 100644 --- a/gems/dry-auto_inject/1.0/how-does-it-work/index.html +++ b/gems/dry-auto_inject/1.0/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject 1.0
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject 1.0
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject 1.0
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject 1.0
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject 1.0
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject 1.0
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-auto_inject main
dry-auto_inject main
Basic usage
Requirements
diff --git a/gems/dry-auto_inject/main/basic-usage/index.html.gz b/gems/dry-auto_inject/main/basic-usage/index.html.gz index 47c9133fcb..3e7de7bfb5 100644 Binary files a/gems/dry-auto_inject/main/basic-usage/index.html.gz and b/gems/dry-auto_inject/main/basic-usage/index.html.gz differ diff --git a/gems/dry-auto_inject/main/how-does-it-work/index.html b/gems/dry-auto_inject/main/how-does-it-work/index.html index 0d4cc36e49..f24fde1a28 100644 --- a/gems/dry-auto_inject/main/how-does-it-work/index.html +++ b/gems/dry-auto_inject/main/how-does-it-work/index.html @@ -3,7 +3,7 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-auto_inject main
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
+});dry-auto_inject main
How does it work?
dry-auto_inject enables constructor dependency injection for your objects. It achieves this by defining two methods in the module that you include in your class.
First, it defines .new, which resolves your dependencies from the container, if you haven't otherwise provided them as explicit arguments. It then passes these dependencies as arguments onto #initialize, as per Ruby’s usual behaviour.
dry-auto_inject main
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
+});dry-auto_inject main
Introduction
dry-auto_inject provides low-impact dependency injection and resolution support for your classes.
It’s designed to work with a container that holds your application’s dependencies. It works well with dry-container, but supports any container that responds to the #[] interface.
dry-auto_inject main
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
+});dry-auto_inject main
Injection strategies
dry-auto_inject supports three injection strategies, allowing you to design and integrate with different kinds of classes.
These strategies all provide constructor dependency injection: dependencies are passed when creating your objects. The strategies differ in how they expect dependencies to be passed to the initializer.
dry-cli 0.4
Arguments
An argument is a token passed after the command name. +});
dry-cli 0.4
Arguments
An argument is a token passed after the command name.
For instance, given the foo greet command, when an user types foo greet Luca, then Luca is considered an argument.
A command can accept none or many arguments.
An argument can be declared as required.
dry-cli 0.4
Callbacks
Third party gems can register before and after callbacks to enhance a command.
+});dry-cli 0.4
Callbacks
Third party gems can register before and after callbacks to enhance a command.
diff --git a/gems/dry-cli/0.4/callbacks/index.html.gz b/gems/dry-cli/0.4/callbacks/index.html.gz
index d6b7bdc03b..f4a383369c 100644
Binary files a/gems/dry-cli/0.4/callbacks/index.html.gz and b/gems/dry-cli/0.4/callbacks/index.html.gz differ
diff --git a/gems/dry-cli/0.4/commands/index.html b/gems/dry-cli/0.4/commands/index.html
index 31bfd09c08..a0880e2a94 100644
--- a/gems/dry-cli/0.4/commands/index.html
+++ b/gems/dry-cli/0.4/commands/index.html
@@ -3,7 +3,7 @@
indexName: 'dry-rb',
inputSelector: '#search-input',
debug: false // Set debug to true if you want to inspect the dropdown
-});Github
dry-cli 0.4
Commands
A command is a subclass of Dry::CLI::Command and it must respond to #call(*).
dry-cli 0.4
Commands
A command is a subclass of Dry::CLI::Command and it must respond to #call(*).
For a given command name, you can register a corresponding command.
diff --git a/gems/dry-cli/0.4/commands/index.html.gz b/gems/dry-cli/0.4/commands/index.html.gz index 59a12518c9..e058e7ad40 100644 Binary files a/gems/dry-cli/0.4/commands/index.html.gz and b/gems/dry-cli/0.4/commands/index.html.gz differ diff --git a/gems/dry-cli/0.4/file-utilities/index.html b/gems/dry-cli/0.4/file-utilities/index.html index d030b7e5e2..38a7e785b6 100644 --- a/gems/dry-cli/0.4/file-utilities/index.html +++ b/gems/dry-cli/0.4/file-utilities/index.html @@ -3,6 +3,6 @@ indexName: 'dry-rb', inputSelector: '#search-input', debug: false // Set debug to true if you want to inspect the dropdown -});dry-cli 0.4
File Utilities
File utilities are a set of useful methods to manipulate files and directories, which must be required manually. API doc
+});dry-cli 0.4
File Utilities
File utilities are a set of useful methods to manipulate files and directories, which must be required manually. API doc
require 'dry/cli/utils/files'