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
The express-http-context seems to be working well with most of the npm packages we are using but odbc. When I checked with them it looks like some changes might be required in the odbc package to support this.
Please take a look at the below link where I have mentioned that issue and the response I have from the owner of express-http-context npm module.
Hi @ranjithchev, Thanks for reporting this. I've only seen express-http-context in passing but it did pique my interest. After looking a little bit into this issue, I've discovered that I don't know enough about cls, cls-hooked, or async_hooks to be able to take a stab at this quickly.
I tried to follow some of the other issues, but didn't really find a good example that would help me to adapt odbc for this. Hopefully someone else can help out.
Hi
The express-http-context seems to be working well with most of the npm packages we are using but odbc. When I checked with them it looks like some changes might be required in the odbc package to support this.
Please take a look at the below link where I have mentioned that issue and the response I have from the owner of express-http-context npm module.
skonves/express-http-context#18
The text was updated successfully, but these errors were encountered: