From a7c4165a4ecd65c99f69c7bc809ddd60a4adf88b Mon Sep 17 00:00:00 2001 From: josieusa Date: Tue, 10 Jan 2017 10:46:02 +0100 Subject: [PATCH] Edit docs of bind option of getCurrentContext() --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b1d8925..0b078f8 100644 --- a/README.md +++ b/README.md @@ -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