We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Given that the concepts of Components are heavy in this toolset, I can't help but think of parent-child relationships and UI events.
I'm working on an example app that adds children to a parent via the parent's + button click, and removing children via the child's - button click.
The question becomes, how does a parent get notified that a child needs to be destroyed?
Parent: https://gist.github.com/jaygarcia/2157f7abac0a46449103 Child: https://gist.github.com/jaygarcia/af7cf118071b9c68c2eb
Demo: http://www.screencast.com/t/DGCKSQ8zYNU
The text was updated successfully, but these errors were encountered:
You can check out the React documentation for this :) http://facebook.github.io/react/tips/communicate-between-components.html
Sorry, something went wrong.
Thanks Dude! It took some studying of that example because the guide only spoke to native elements.
I figured it out though =).
Almost done w/ my blog example. Gotta get that auto-viewport-resize thing working.
Do you know Context on React-native!
No branches or pull requests
Given that the concepts of Components are heavy in this toolset, I can't help but think of parent-child relationships and UI events.
I'm working on an example app that adds children to a parent via the parent's + button click, and removing children via the child's - button click.
The question becomes, how does a parent get notified that a child needs to be destroyed?
Parent: https://gist.github.com/jaygarcia/2157f7abac0a46449103
Child: https://gist.github.com/jaygarcia/af7cf118071b9c68c2eb
Demo: http://www.screencast.com/t/DGCKSQ8zYNU
The text was updated successfully, but these errors were encountered: