-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #85 from godrose/develop
chore: merge from develop
- Loading branch information
Showing
85 changed files
with
742 additions
and
276 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
30 changes: 0 additions & 30 deletions
30
Solid.IoC.Adapters.BoDi.Specs/Solid - Backup.IoC.Adapters.BoDi.Specs.csproj
This file was deleted.
Oops, something went wrong.
6 changes: 3 additions & 3 deletions
6
Solid.IoC.Adapters.BoDi.Specs/Solid.IoC.Adapters.BoDi.Specs.csproj
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
namespace Solid.IoC.Registration.Specs.Tests.Contracts | ||
{ | ||
public interface IDependency | ||
{ | ||
|
||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
namespace Solid.IoC.Registration.Specs.Tests.Contracts | ||
{ | ||
public abstract class ObjectBase | ||
{ | ||
|
||
} | ||
} |
9 changes: 9 additions & 0 deletions
9
Solid.IoC.Registration.Specs.Tests.Implementations/Dependency.cs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
using Solid.IoC.Registration.Specs.Tests.Contracts; | ||
|
||
namespace Solid.IoC.Registration.Specs.Tests.Implementations | ||
{ | ||
public class Dependency : IDependency | ||
{ | ||
|
||
} | ||
} |
43 changes: 33 additions & 10 deletions
43
Solid.IoC.Registration.Specs/Automagical Registration.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,45 @@ | ||
Feature: Automagical Registration | ||
@cleanRegistrationMethodContext | ||
Feature: Automagical Registration | ||
In order to simplify IoC implementation in my apps | ||
As an app developer | ||
I want to be able to register dependencies automagically | ||
|
||
Scenario: Registering dependencies automagically by ending should allow successful resolution | ||
Scenario Outline: Registering dependencies automagically by ending should allow successful resolution | ||
Given There are valid implementations for all declared dependencies | ||
When I use object container | ||
When I use '<container name>' | ||
When I use registration by ending | ||
Then All dependencies can be resolved successfully | ||
Then All dependencies by ending can be resolved successfully | ||
Examples: | ||
| container name | | ||
| specflow object container | | ||
| microsoft di container | | ||
|
||
Scenario: Registering dependencies automagically by contract which is an interface should allow successful resolution | ||
Scenario Outline: Registering dependencies automagically by contract which is an interface should allow successful resolution | ||
Given There are valid implementations for all declared dependencies | ||
When I use object container | ||
When I use '<container name>' | ||
When I use registration by contract which is an interface | ||
Then All dependencies can be resolved successfully | ||
Then All dependencies by contract which is an interface can be resolved successfully | ||
Examples: | ||
| container name | | ||
| specflow object container | | ||
| microsoft di container | | ||
|
||
Scenario: Registering dependencies automagically by contract which is a class should allow successful resolution | ||
Scenario Outline: Registering dependencies automagically by contract which is a class should allow successful resolution | ||
Given There are valid implementations for all declared dependencies | ||
When I use object container | ||
When I use '<container name>' | ||
When I use registration by contract which is a class | ||
Then All dependencies can be resolved successfully | ||
Then All dependencies by contract which is a class can be resolved successfully | ||
Examples: | ||
| container name | | ||
| specflow object container | | ||
| microsoft di container | | ||
|
||
Scenario Outline: Registering all dependencies automagically with implicit default registration method should allow successful resolution for all dependencies | ||
Given There are valid implementations for all declared dependencies | ||
When I use '<container name>' with default registration method | ||
When I use automagical registration | ||
Then All dependencies can be resolved successfully | ||
Examples: | ||
| container name | | ||
| specflow object container | | ||
| microsoft di container | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.