1047af4e76
Document in README.md and test correct usage of cls-hooked
2016-09-09 14:37:24 +02:00
38f6110eff
Use cls-hooked instead of continuation-local-storage,
...
as suggested by @raymondfeng
in strongloop/loopback-context PR #1 comment #235931961
2016-09-09 14:37:24 +02:00
f120f2e431
Revert "Lazy-load CLS module"
2016-09-09 14:37:24 +02:00
c96e37c99d
Merge upstream/master into master to sync with upstream repo
...
Fix comment
2016-09-09 14:27:29 +02:00
8433e75a24
make warning less ambigious
2016-09-09 10:27:37 +02:00
1fd90e0a48
1.0.0
...
* First release!
2016-09-09 10:27:37 +02:00
4e4ed1d8a2
Add big fat warning to README
...
Recommend against using this module.
2016-09-09 10:27:37 +02:00
404c27bd5b
API cleanup
...
Rename "per-request-context" middleware to shorter "per-request".
Introduce "LoopBackContext.perRequest" as a shortcut for way too long
"loopback-context/server/middlewar/per-request"
2016-09-09 10:27:37 +02:00
40672a7e29
Enable Travis CI
2016-08-02 14:41:24 +02:00
12a7113aeb
fixup! style
2016-08-02 14:41:24 +02:00
df60f13f4d
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-08-02 14:41:24 +02:00
2a0bbb3c77
Rename to loopback-context/LoopBackContext
2016-08-02 14:41:24 +02:00
c7e8bf7001
Initial implementation
2016-08-02 14:41:24 +02:00
c8daeb5587
Rename to loopback-context
...
Also change the npm version to 1.0.0, so that we don't have to modify
downstream loopback pull request after we make the first release.
2016-07-29 09:16:11 +02:00
63d031422d
Initial commit
2016-07-28 15:11:12 +02:00
josieusa
Carl Fürstenberg
Miroslav Bajtoš