From d7e85c3fe0d98ac28844c06b1f1def980bd193d1 Mon Sep 17 00:00:00 2001 From: Rob Levin Date: Mon, 11 Oct 2021 09:39:51 -0700 Subject: [PATCH] Update node.md (#1016) Since it's much. more likely that consumers will want a Promise, Observable, or other asynchronous mechanism to listen for the flag enabled callback, add a link out to those docs. This took our team a while to find fwiw. --- websitev2/docs/sdks/node.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/websitev2/docs/sdks/node.md b/websitev2/docs/sdks/node.md index 44776b82ad..786c5b5ad4 100644 --- a/websitev2/docs/sdks/node.md +++ b/websitev2/docs/sdks/node.md @@ -52,6 +52,8 @@ Please note that in the above example we put the isEnabled-evaluation inside the It can also be nice to notice that if you use an undefined feature toggle the Unleash SDK will return false instead of crashing your application. The SDK will also report metrics back to Unleash-hosted on feature toggle usage, which makes it \_possible to spot toggles not yet defined. And this is a very neat way to help you debug if something does not work as expected. +_Note that you can also wait until the Unleash SDK has fully syncrhonized similar to familiar "on-ready" hooks in other APIs. See [block until Unleashed is synchronized](https://github.com/Unleash/unleash-client-node#block-until-unleash-sdk-has-synchronized) for how to do this._ + ## Step 4: Provide the Unleash-context {#step-4-provide-the-unleash-context} It is the client SDK that computes whether a feature toggle should be considered enabled or disabled for a specific request. This is the job of the activation strategies, which are implemented in the client SDK.