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
{{ message }}
This repository was archived by the owner on Dec 27, 2024. It is now read-only.
Each request should be it's own zone context. This will allow for shared state through a request... for example a DB handling function that doesn't have access to express.Request would still have access to the current zone context for the purpose of exchange data across that request.
... https://expressjs.com/en/4x/api.html#res.locals
The advantage of using zones is that we won't have to pass around a reference to res.locals in functions that otherwise wouldn't have access to that.
I'm developing doubts that this should be a core implementation... If someone really wants Zonejs they could inject it in their own middleware early on, so it may not make sense to burden all users with this as many may not find it desirable.
Each request should be it's own zone context. This will allow for shared state through a request... for example a DB handling function that doesn't have access to
express.Request
would still have access to the current zone context for the purpose of exchange data across that request.... https://expressjs.com/en/4x/api.html#res.locals
The advantage of using zones is that we won't have to pass around a reference to res.locals in functions that otherwise wouldn't have access to that.
See:
The text was updated successfully, but these errors were encountered: