From 9460263e414cde568af439d341ec95d27ed4893d Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Mon, 9 May 2016 02:35:48 +0100 Subject: [PATCH] Merge pull request #6730 from elas7/fix-docs [docs] Remove mention of 'nested object' as an allowed children in React.Children.map (cherry picked from commit 982e096eb56d46406b6a33ea8131bf9bbd0fe63e) --- docs/docs/ref-01-top-level-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/ref-01-top-level-api.md b/docs/docs/ref-01-top-level-api.md index 24252f8e73..31aa0f92dd 100644 --- a/docs/docs/ref-01-top-level-api.md +++ b/docs/docs/ref-01-top-level-api.md @@ -98,7 +98,7 @@ Verifies the object is a ReactElement. array React.Children.map(object children, function fn [, object thisArg]) ``` -Invoke `fn` on every immediate child contained within `children` with `this` set to `thisArg`. If `children` is a nested object or array it will be traversed: `fn` will never be passed the container objects. If children is `null` or `undefined` returns `null` or `undefined` rather than an array. +Invoke `fn` on every immediate child contained within `children` with `this` set to `thisArg`. If `children` is a [keyed fragment](/react/docs/create-fragment.html) or array it will be traversed: `fn` will never be passed the container objects. If children is `null` or `undefined` returns `null` or `undefined` rather than an array. #### React.Children.forEach