Adding service dependency injection feature for Services

[SimonDarksideJ]

Reality Collective - Service Framework Pull Request

Overview

Adding the much anticipated Dependency Injection feature, which allows constructors like the following

public DependencyTestService2(string name, uint priority, BaseProfile profile, IParentService parentService)

So long as the dependent service is registered in the Service Configuration PRIOR to the above service being registered, it will automatically inject the reference to the existing registered service.
Removes the need for unnecessary service wind up functionality within a service.

Changes

• Adds a new TryGetService call for simplification
• Adds dependency check if there are additional service interfaces included in the primary constructor

Note

Only the primary constructor is inspected and ONLY parameters deriving from IService will be included. Any other types of parameters are likely to introduce errors.

Breaking Changes

• None

Testing status

• Includes unit tests.

Notes

This is designed for Services only at present. Modules will be evaluated in future updates

[FejZa]

Will this always assume the first service is the parent service and following are dependencies?

[SimonDarksideJ]

Will this always assume the first service is the parent service and following are dependencies?

The first 3 parameters are mandatory for the service registration, any ADDITIONAL parameters need to be based upon IService and you can add as many as you like (so long as their services are registered before this service in the Service COnfiguration, e.g:
A basic service

public DependencyTestService2(string name, uint priority, BaseProfile profile)

A service with one dependency

public DependencyTestService2(string name, uint priority, BaseProfile profile, IParentService parentService)

A service with multiple dependencies

public DependencyTestService2(string name, uint priority, BaseProfile profile, IServiceDependency1 dependentService1, IServiceDependency2 dependentService2, IServiceDependency3 dependentService3)

Only caveat, is that all parameters AFTER BaseProfile (or CustomProfile for services with a custom profile) MUST be inheritable from IService, else it will throw an error when it is registered.

[SimonDarksideJ]

Will this always assume the first service is the parent service and following are dependencies?

Actually, I've not tested with with ServiceModules only base services.

Do we also need the injection to work on modules as well? Or should we complete this first and then look at modules, which "technically" already accept/expect a service as a parent as the next parameter.

[FejZa]

I fear people will assume it works for modules as well. But I think for a first version we can omit it and keep it in the preview release until we have added modules as well