verdnatura-mirror
/
loopback-context
mirror of https://github.com/strongloop/loopback-context.git
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Edit docs of bind option of getCurrentContext()

This commit is contained in:
josieusa 2017-01-10 10:46:02 +01:00
parent c836f5f096
commit a7c4165a4e
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -72,9 +72,11 @@ in this example:
var ctx = LoopBackContext.getCurrentContext({ bind: true });
The `bind` option defaults to `false` (only in order to prevent breaking legacy
apps). But if you are writing a new app, for example, you can safely use
`bind: true` everywhere in your app.
The `bind` option defaults to `false`. This is only in order to prevent breaking
legacy apps; but if your app doesn't have such issue, then you can safely use
`bind: true` everywhere in your app (e.g. with a
[codemod](https://github.com/facebook/jscodeshift), or by monkey-patching
`getCurrentContext()` globally, if you prefer an automated fashion).
**Warning**: this only applies to application modules. In fact, if the module
affected by the concurrency issue is of this kind, you can easily refactor/write