One of react&#x27;s core tenets is unidirectional data flow.  Trying to use it in a bidirectional way is... painful.  There is also a struggle with state vs props.  The quick version is that state is internal to a component and is changeable directly by it, and props are given out by the parent and are not directly changeable.<p>Generally the way the bidirectional issue is solved is by closing the loop via dispatchers and stores.  The child components send out actions to the stores, which then flow down through the parent, back in to the child.  Turning what used to be a bidirectional flow to a unidirectional flow (sometimes at the cost of a bit of boilerplate for pre-existing components).<p>I guess the real question is, what is the use for the parent to be able to see the &#x27;state&#x27; (the child components internal state)?  The answer to that question (in my limited experience) has often been either &#x27;to trigger an event (ex: save a form)&#x27; or &#x27;so the parent can make some other rendering decision&#x27;.  Both of which I&#x27;ve generally been able to solve via a flux implementation and possibly changing a &#x27;state&#x27; into a &#x27;prop&#x27; in the child (where the child gets a prop, some action is taken, and instead of changing state internally, an event is dispatched to the store with the new data, and the parent rerenders the child with the new &#x27;prop&#x27;).<p>But ultimately, hack it how you need.  It&#x27;s your code after all.