You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jmcdo29 opened this issue
Mar 11, 2020
· 0 comments
Assignees
Labels
core 📖Functionality related to the service or module classesHas PRThis issue has a PR related to it, or is in a branch in developmentReadyThis issue has been taken care of and is waiting to be merged
As #9 is already a breaking change, might as well make things easier for the every day developer as well by masking the forRoot(OgmaModule, options) functionality behind a core module that sits in the background so that all is needed is OgmaModule.forRoot(options) or OgmaModule.forRoorAsync(asyncOptions). This should be easy enough to implement for anyone who wants to manage it.
The text was updated successfully, but these errors were encountered:
Oh where to begin? This rewrite allows for the OgmaModule to manage so much more than just HTTP, and
in such a way that it's almost hard to describe. With the plugin system created, so long as a class
extends the `AbstractInterceptorService` **and** the class does not have any extra injections
needed, any class can be provided to the `interceptor` property of the `OgmaModuleOptions` to allow
for interceptor request parsing. By default, the class that is provided is a
`NoopInterceptorService` that really should only be there so an error gets thrown, but something had
to be there for the Nest DI ssytem to not complain. Tests are still to come to help clean out dead
code, but overall, the proof of concept is there and it works!
re #7#8#9#10#11
Oh where to begin? This rewrite allows for the OgmaModule to manage so much more than just HTTP, and
in such a way that it's almost hard to describe. With the plugin system created, so long as a class
extends the `AbstractInterceptorService` **and** the class does not have any extra injections
needed, any class can be provided to the `interceptor` property of the `OgmaModuleOptions` to allow
for interceptor request parsing. By default, the class that is provided is a
`NoopInterceptorService` that really should only be there so an error gets thrown, but something had
to be there for the Nest DI ssytem to not complain. Tests are still to come to help clean out dead
code, but overall, the proof of concept is there and it works!
re #7#8#9#10#11
core 📖Functionality related to the service or module classesHas PRThis issue has a PR related to it, or is in a branch in developmentReadyThis issue has been taken care of and is waiting to be merged
As #9 is already a breaking change, might as well make things easier for the every day developer as well by masking the
forRoot(OgmaModule, options)
functionality behind a core module that sits in the background so that all is needed isOgmaModule.forRoot(options)
orOgmaModule.forRoorAsync(asyncOptions)
. This should be easy enough to implement for anyone who wants to manage it.The text was updated successfully, but these errors were encountered: