-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Microservice Support #7
Labels
Milestone
Comments
jmcdo29
added
enhancement
help wanted 🆘
Extra attention is needed
good first issue 👍
Good for newcomers
labels
Mar 2, 2020
jmcdo29
added a commit
that referenced
this issue
Mar 27, 2020
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
Will open a new issue with specified parsers |
jmcdo29
added a commit
that referenced
this issue
Jun 20, 2021
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add support to the Module to support calls to and from Microservice, to give a better tracking context of the request throughout the server.
The text was updated successfully, but these errors were encountered: