In React, the general rule is: data flows in one direction – down. Without getting into data sharing processes like Context or Redux, generally speaking, in React, data flows down from parents to children. That is one of the things that makes React so efficient.<\/p>\n
However, data can in effect be “passed up” to a Parent using a callback function defined in the Parent. That callback is passed down to the Child as a prop using a custom “on” event key name, like onDoCallback. <\/p>\n
For example, a callback function called doCallback() defined in the Parent can be passed down to the Child as a prop like this: The Child component function then takes in the custom “on” event name { onDoCallback } as a prop, and uses it to execute the callback function defined in the Parent. So in the Child, calling onDoCallback(data) is in effect, executing the function doCallback(data) in the Parent. The (data) parameter is provided to the Parent function from the Child, so you could say, data is being passed up to the Parent.<\/p>\n It can look something like this:<\/p>\n Parent.js<\/strong><\/p>\n Child.js<\/strong><\/p>\n When the form is submitted in the Child, the Child’s newData is passed to the doCallback function in the Parent, which then can be used to update state. <\/p>\n <\/p>\n The process is similar, but slightly different. <\/p>\n In this case, like the previous example, the doCallback() function is defined in the top component, let’s say the Grandparent. The Grandparent passes the doCallback() to it’s child (Parent) as a prop using a custom “on” event keyname, much like the previous example: <\/p>\n \t The Parent component function takes { onDoCallback } as a prop, and simply passes it to the child component. But notice there is one subtle difference in the way it is passed. Instead of using onDoCallback={doCallback}, the Parent uses onDoCallback={onDoCallback} The key and the value are the same value.<\/p>\n \t So it would look something like this:<\/p>\n GrandParent.js<\/strong><\/p>\n Parent.js<\/strong><\/p>\n Child.js<\/strong> —————————-<\/p>\n Now, when the Child fires off onDoCallback(newData) <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" In React, the general rule is: data flows in one direction – down. Without getting into data sharing processes like Context or Redux, generally speaking, in React, data flows down from parents to children. That is one of the things that makes React so efficient. However, data can in effect be “passed up” to a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-942","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\n
\n\t <Child onDoCallback={doCallback} \/><\/code><\/p>\nconst [parentData, setParentData]=useState(\"\")
\n function Parent() {
\n function doCallback(data)<\/strong> {
\n setParentData(data)
\n }
\n return (
\n <div >
\n <Child onDoCallback={doCallback}<\/strong> \/>
\n <\/div>
\n )
\n }
\n export default Parent;<\/code><\/p>\n function Child({ onDoCallback }<\/strong>) {
\n const [formData, setFormData]=useState(\"\")
\n function handleSubmit(event) {
\n event.preventDefault()
\n const newData={
\n formData
\n }
\n onDoCallback(newData)<\/strong>
\n }
\n return (
\n <div>
\n <form onSubmit={handleSubmit}>
\n <input type=\"text\" id=\"formData\"
\n\t value={formData}
\n\t onChange={e => setFormData(e.target.value)}
\n\t \/>
\n <button type=\"submit\">Add Data<\/button>
\n <\/form>
\n <\/div>
\n )
\n }
\n export default Child;<\/code><\/p>\nBut what about passing data from a Child to a Grandparent<\/em> (or GreatGrandparent)? <\/h3>\n
<Parent onDoCallback={doCallback} \/><\/code><\/p>\n <Child onDoCallback={onDoCallback}<\/strong> \/><\/code><\/p>\n const [grandParentData, setGrandParentData]=useState(\"\")
\n function GrandParent() {
\n function doCallback(data)<\/strong> {
\n setGrandParentData(data)
\n }
\n return (
\n <div >
\n <Parent onDoCallback={doCallback}<\/strong> \/>
\n <\/div>
\n )
\n }
\n export default Parent;<\/code><\/p>\n function Parent({ onDoCallback }<\/strong>) {
\n \/\/ other Parent code
\n return (
\n <div >
\n <Child onDoCallback={onDoCallback}<\/strong> \/>
\n <\/div>
\n )
\n }
\n export default Parent;<\/code><\/p>\n
\n function Child({ onDoCallback }<\/strong>) {
\n const [formData, setFormData]=useState(\"\")
\n function handleSubmit(event) {
\n event.preventDefault()
\n const newData={
\n formData
\n }
\n onDoCallback(newData)<\/strong>
\n }
\n return (
\n <div>
\n <form onSubmit={handleSubmit}>
\n <input type=\"text\" id=\"formData\"
\n\t value={formData}
\n\t onChange={e => setFormData(e.target.value)}
\n\t \/>
\n <button type=\"submit\">Add Data<\/button>
\n <\/form>
\n <\/div>
\n )
\n }
\n export default Child;<\/code><\/p>\n
\nit is, in effect, passing data from Child to a function in the GrandParent.<\/p>\n