Skip to content
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

Closed
jmcdo29 opened this issue Mar 2, 2020 · 1 comment
Closed

Add Microservice Support #7

jmcdo29 opened this issue Mar 2, 2020 · 1 comment
Labels
good first issue 👍 Good for newcomers help wanted 🆘 Extra attention is needed

Comments

@jmcdo29
Copy link
Owner

jmcdo29 commented Mar 2, 2020

Add support to the Module to support calls to and from Microservice, to give a better tracking context of the request throughout the server.

@jmcdo29 jmcdo29 added enhancement help wanted 🆘 Extra attention is needed good first issue 👍 Good for newcomers labels Mar 2, 2020
@jmcdo29 jmcdo29 modified the milestones: 3.0, 3.0.0 Mar 11, 2020
jmcdo29 added a commit that referenced this issue Mar 13, 2020
Creates interfaces and services that should handle the logic for the HTTP,
 WS, and RPC logging. This is a broken build and it is expected for CI to f
ail.

re #7 #8 #9
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
@jmcdo29
Copy link
Owner Author

jmcdo29 commented Mar 28, 2020

Will open a new issue with specified parsers

@jmcdo29 jmcdo29 closed this as completed Mar 28, 2020
jmcdo29 added a commit that referenced this issue Jun 20, 2021
Creates interfaces and services that should handle the logic for the HTTP,
 WS, and RPC logging. This is a broken build and it is expected for CI to f
ail.

re #7 #8 #9
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
Labels
good first issue 👍 Good for newcomers help wanted 🆘 Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant