Skip to content

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

Notifications You must be signed in to change notification settings

azatoth/loopback-context

 
 

Repository files navigation

loopback-context

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

WARNING

We recommend AGAINST using the loopback-context module until there is a stable solution to the issue below!

The module node-continuation-local-storage is known to have many problems, see e.g. issue #59. As a result, loopback-context does not work in many situations, as can be seen from issues reported in LoopBack's issue tracker.

If you are running on Node v6, you can try the new alternative cls-hooked.

Usage

  1. Add per-request middleware to your server/middleware-config.json:
{
  "initial": {
    "loopback-context#per-request": {
    }
  }
}
  1. 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' });
});

See the official LoopBack documentation for more details.

About

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

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 100.0%