From 69bc2ea5755b3182483eb86951486ef39cc94ea3 Mon Sep 17 00:00:00 2001 From: Jamie Dixon Date: Wed, 27 May 2020 20:08:10 +0100 Subject: [PATCH] Document changes to fromNode that allow the return fn to be partially applied in some cases --- docs/src/pages/docs/crocks/Async.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/docs/crocks/Async.md b/docs/src/pages/docs/crocks/Async.md index 3a9173bd7..5aeb955cb 100644 --- a/docs/src/pages/docs/crocks/Async.md +++ b/docs/src/pages/docs/crocks/Async.md @@ -379,8 +379,14 @@ As such, the need for binding may arise. `fromNode` provides a second, optional argument that takes the context that will be used to bind the function being wrapped. -Any curried interface will not be respected and if a curried interface is needed -then [`nAry`][nary] can be used. +The function returned from `fromNode` will be automatically curried, allowing you +to partially apply the function so long as the arity of the original function given +to `fromNode` can be determined via its `.length` property. + +In practice this means that functions defined via `compose` or those making use +of `argument`, spread args (`...args`) or default values for parameters, will not be +good candidates for partial application. +