How to read React.Children.map api notation?
up vote
0
down vote
favorite
Looking at the code for React.Children.map, it looks like the function takes up to 3 args.
The api doc for React.Children.map shows
React.Children.map(children, function[(thisArg)])
If it can take 3 args I expected to see 2 commas in there somewhere.
My question is
How do you read React.Children.map(children, function[(thisArg)])
in plain english?
So far I have "React.Children.map is a function that..."
reactjs
add a comment |
up vote
0
down vote
favorite
Looking at the code for React.Children.map, it looks like the function takes up to 3 args.
The api doc for React.Children.map shows
React.Children.map(children, function[(thisArg)])
If it can take 3 args I expected to see 2 commas in there somewhere.
My question is
How do you read React.Children.map(children, function[(thisArg)])
in plain english?
So far I have "React.Children.map is a function that..."
reactjs
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Looking at the code for React.Children.map, it looks like the function takes up to 3 args.
The api doc for React.Children.map shows
React.Children.map(children, function[(thisArg)])
If it can take 3 args I expected to see 2 commas in there somewhere.
My question is
How do you read React.Children.map(children, function[(thisArg)])
in plain english?
So far I have "React.Children.map is a function that..."
reactjs
Looking at the code for React.Children.map, it looks like the function takes up to 3 args.
The api doc for React.Children.map shows
React.Children.map(children, function[(thisArg)])
If it can take 3 args I expected to see 2 commas in there somewhere.
My question is
How do you read React.Children.map(children, function[(thisArg)])
in plain english?
So far I have "React.Children.map is a function that..."
reactjs
reactjs
edited Nov 17 at 16:59
asked Nov 10 at 19:00
psalaets
58226
58226
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
function[(thisArg)]
isn't a standard denotation. As the documentation states, map
Invokes a function on every immediate child contained within children with this set to thisArg.
Children.map
signature is similar to JavaScript Array.prototype.map
. There are 3 arguments, 3rd argument is optional this
context for callback function if needed.
Children.map
is documented better in source code:
/**
* Maps children that are typically specified as `props.children`.
*
* See https://reactjs.org/docs/react-api.html#reactchildrenmap
*
* The provided mapFunction(child, key, index) will be called for each
* leaf child.
*
* @param {?*} children Children tree container.
* @param {function(*, int)} func The map function.
* @param {*} context Context for mapFunction.
* @return {object} Object containing the ordered map of results.
*/
function mapChildren(children, func, context) {...}
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used asthis
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.
– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
function[(thisArg)]
isn't a standard denotation. As the documentation states, map
Invokes a function on every immediate child contained within children with this set to thisArg.
Children.map
signature is similar to JavaScript Array.prototype.map
. There are 3 arguments, 3rd argument is optional this
context for callback function if needed.
Children.map
is documented better in source code:
/**
* Maps children that are typically specified as `props.children`.
*
* See https://reactjs.org/docs/react-api.html#reactchildrenmap
*
* The provided mapFunction(child, key, index) will be called for each
* leaf child.
*
* @param {?*} children Children tree container.
* @param {function(*, int)} func The map function.
* @param {*} context Context for mapFunction.
* @return {object} Object containing the ordered map of results.
*/
function mapChildren(children, func, context) {...}
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used asthis
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.
– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
add a comment |
up vote
0
down vote
accepted
function[(thisArg)]
isn't a standard denotation. As the documentation states, map
Invokes a function on every immediate child contained within children with this set to thisArg.
Children.map
signature is similar to JavaScript Array.prototype.map
. There are 3 arguments, 3rd argument is optional this
context for callback function if needed.
Children.map
is documented better in source code:
/**
* Maps children that are typically specified as `props.children`.
*
* See https://reactjs.org/docs/react-api.html#reactchildrenmap
*
* The provided mapFunction(child, key, index) will be called for each
* leaf child.
*
* @param {?*} children Children tree container.
* @param {function(*, int)} func The map function.
* @param {*} context Context for mapFunction.
* @return {object} Object containing the ordered map of results.
*/
function mapChildren(children, func, context) {...}
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used asthis
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.
– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
function[(thisArg)]
isn't a standard denotation. As the documentation states, map
Invokes a function on every immediate child contained within children with this set to thisArg.
Children.map
signature is similar to JavaScript Array.prototype.map
. There are 3 arguments, 3rd argument is optional this
context for callback function if needed.
Children.map
is documented better in source code:
/**
* Maps children that are typically specified as `props.children`.
*
* See https://reactjs.org/docs/react-api.html#reactchildrenmap
*
* The provided mapFunction(child, key, index) will be called for each
* leaf child.
*
* @param {?*} children Children tree container.
* @param {function(*, int)} func The map function.
* @param {*} context Context for mapFunction.
* @return {object} Object containing the ordered map of results.
*/
function mapChildren(children, func, context) {...}
function[(thisArg)]
isn't a standard denotation. As the documentation states, map
Invokes a function on every immediate child contained within children with this set to thisArg.
Children.map
signature is similar to JavaScript Array.prototype.map
. There are 3 arguments, 3rd argument is optional this
context for callback function if needed.
Children.map
is documented better in source code:
/**
* Maps children that are typically specified as `props.children`.
*
* See https://reactjs.org/docs/react-api.html#reactchildrenmap
*
* The provided mapFunction(child, key, index) will be called for each
* leaf child.
*
* @param {?*} children Children tree container.
* @param {function(*, int)} func The map function.
* @param {*} context Context for mapFunction.
* @return {object} Object containing the ordered map of results.
*/
function mapChildren(children, func, context) {...}
answered Nov 10 at 19:45
estus
64k2194201
64k2194201
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used asthis
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.
– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
add a comment |
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used asthis
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.
– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
Thanks for taking the time to respond but this doesn't answer my question. Your answer restates things that I already know from reading the docs and looking at the code. I'm not asking how to use React.Children.map but rather, I want to know how the api notation tells me how to use React.Children.map. Thanks
– psalaets
Nov 17 at 17:02
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used as
this
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.– estus
Nov 17 at 17:14
As I mentioned, that this isn't standard notation. The answer explains what it really stands for. You can read it as React.Children.map is a function that accepts children argument, callback function argument and optional thisArg argument that will be used as
this
context in callback function. Can anyone read it like that without knowing what it stands for? I doubt that.– estus
Nov 17 at 17:14
alright fair enough ✓
– psalaets
Nov 22 at 17:47
alright fair enough ✓
– psalaets
Nov 22 at 17:47
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242398%2fhow-to-read-react-children-map-api-notation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown