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
Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
The FAQ Hybrid Application Page does not mention anything about App Lifecycle Events and Microservice order.
Expected behavior
Explain that Nest App Lifecycle Events start when you call await app.listen and not await app.create
Explain that the order of await app.startAllMicroservices and await app.listen is crucial
Minimal reproduction of the problem with instructions
When utilizing Lifecycle Events such as onApplicationBootstrap / onModuleInit and consuming app's functionality inside Microservices, it is important to clarify that the order of the bootstrap lines plays an essential role:
The lifecycle events will complete before the microservices have started.
We had a bug when our application started and a microservice was immediately consumed, before our Promises from modules' OnModuleInit functions have finished, throwing errors obviously.
What is the motivation / use case for changing the behavior?
To educate developers and to avoid future bugs. Had to debug your code to figure these things out...
Environment
For Tooling issues:
Node version: 18.3.0
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
The FAQ Hybrid Application Page does not mention anything about App Lifecycle Events and Microservice order.
Expected behavior
await app.listen
and notawait app.create
await app.startAllMicroservices
andawait app.listen
is crucialMinimal reproduction of the problem with instructions
When utilizing Lifecycle Events such as
onApplicationBootstrap
/onModuleInit
and consuming app's functionality inside Microservices, it is important to clarify that the order of the bootstrap lines plays an essential role:For example:
The lifecycle events will complete after the microservices have started.
The lifecycle events will complete before the microservices have started.
We had a bug when our application started and a microservice was immediately consumed, before our Promises from modules'
OnModuleInit
functions have finished, throwing errors obviously.What is the motivation / use case for changing the behavior?
To educate developers and to avoid future bugs. Had to debug your code to figure these things out...
Environment
For Tooling issues:
The text was updated successfully, but these errors were encountered: