Initialize context from middleware and not on get

[chenrozenes]

When running the entire express app inside a domain context, the domain.active has value.
If we call get/getContext for the first time, it will initialize the ___$cntxt___ object before we created our request context domain.
In this situation the middleware will not create another domain, and the outer domain will be used for all requests.
The problematic flow is this:

// Running inside a domain context (aka domain X)

// Somewhere we do...
contextService.get('request');

// express's middleware declaration
app.use(contextService.middleware('request')) // Another domain hasn't been created

// inside an express route
contextService.set('request:userId', '123'); // value saved on domain X

The fix will initialize the context object only within the middleware, get and set calls will address the request-context domain only

[michaelkrone]

@chenrozenes
I did not look into this yet, but why the close?

[chenrozenes]

@michaelkrone I ran another test of mine that suddenly didn't work so I closed it until I'll figure it out, but all good

[michaelkrone]

OK, I will look into this tonight and publish a new version if it looks ok.

[chenrozenes]

@michaelkrone Hey, have you checked it out?

[michaelkrone]

Sorry for the delay. Will publish 1.0.1 2.0.0 now.