Current context for LoopBack applications, based on node-continuation-local-storage

Go to file

Miroslav Bajtoš 1f214bf3ba Lazy-load CLS module As soon as CLS module is loaded, the instrumentation/patching of async-listener is fired. This may cause stack overflows due to promise instrumentation. By loading CLS module lazily (only when used for real), we avoid this kind of problems in applications that are not using current-context at all.		2016-07-29 09:36:34 +02:00
browser	Rename to loopback-context/LoopBackContext	2016-07-29 09:36:34 +02:00
server	Lazy-load CLS module	2016-07-29 09:36:34 +02:00
test	Rename to loopback-context/LoopBackContext	2016-07-29 09:36:34 +02:00
.eslintignore	Initial commit	2016-07-28 15:11:12 +02:00
.eslintrc	Initial commit	2016-07-28 15:11:12 +02:00
.gitignore	Initial commit	2016-07-28 15:11:12 +02:00
CONTRIBUTING.md	Initial commit	2016-07-28 15:11:12 +02:00
README.md	Rename to loopback-context/LoopBackContext	2016-07-29 09:36:34 +02:00
package.json	Initial implementation	2016-07-29 09:17:04 +02:00

README.md

loopback-context

Current context for LoopBack applications, based on node-continuation-local-storage.

Usage

Add per-request-context middleware to your server/middleware-config.json:

{
  "initial": {
    "loopback-context#per-request-context": {
    }
  }
}

Then you can access the context from your code:

var LoopBackContext = require('loopback-context');

// ...

MyModel.myMethod = function(cb) {
  var ctx = LoopBackContext.getCurrentContext();
  ctx.get('key');
  ctx.set('key', { foo: 'bar' });
});