From 2e704cafff92b79a4fc6ab4b8891cb4fec9b6ad2 Mon Sep 17 00:00:00 2001 From: karanbhomiagit Date: Sun, 14 Oct 2018 21:58:42 +0530 Subject: [PATCH] Update index.md (#18531) --- .../pages/guide/english/javascript/callback-functions/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/client/src/pages/guide/english/javascript/callback-functions/index.md b/client/src/pages/guide/english/javascript/callback-functions/index.md index 52bd2cf6e0..30dc4a5808 100644 --- a/client/src/pages/guide/english/javascript/callback-functions/index.md +++ b/client/src/pages/guide/english/javascript/callback-functions/index.md @@ -77,3 +77,5 @@ serverRequest("The glass is half ", getResults); In the above example, we make a mock request to a server. After 5 seconds elapse the response is modified and then our callback function `getResults` gets executed. To see this in action, you can copy/paste the above code into your browser's developer tool and execute it. Also, if you are already familiar with `setTimeout`, then you've been using callback functions all along. The anonymous function argument passed into the above example's `setTimeout` function call is also a callback! So the example's original callback is actually executed by another callback. Be careful not to nest too many callbacks if you can help it, as this can lead to something called "callback hell"! As the name implies, it isn't a joy to deal with. + +Please refer to this link for more details on "callback hell" : http://callbackhell.com/