Change in typedi ^0.9.0 appears to break the detection of services registered in nodepay-core. Issue is not addressed with even the @Service decorator on every participating class, hinting at a possible issue with the mechanism, ie. a bug in typedi.
As a workaround, this PR converts the settings manager into a base gateway instance member, rendering it available to each gateway strategy separately. Dependency injection is still preferred, and should be investigated separately.
See https://github.com/typestack/routing-controllers/issues/642
Change in typedi
^0.9.0appears to break the detection of services registered innodepay-core. Issue is not addressed with even the@Servicedecorator on every participating class, hinting at a possible issue with the mechanism, ie. a bug in typedi.As a workaround, this PR converts the settings manager into a base gateway instance member, rendering it available to each gateway strategy separately. Dependency injection is still preferred, and should be investigated separately.