You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our projects, we create a common directory inside the main js directory. This folder houses commonly-reused components throughout the app. For example, we can declare common Text and Header components...
It could be remedied by making available a default ref root which points to the root node. This would allow generic forwarding to be written into a base class, which other components could inherit from:
This would essentially forward the props down the chain until we hit a "concrete" built-in component. Any arguments against making a root ref available by default?
The text was updated successfully, but these errors were encountered:
In React Native, TouchableHighlight requires its children to forward 'setNativeProps'. This is implemented in built-in components, but must be manually implemented for all custom components.
This causes big incompatibilities with a library like Native Base, not to mention any custom components that the developer creates, which is apparently a preferred pattern for theming:
It could be remedied by making available a default ref
root
which points to the root node. This would allow generic forwarding to be written into a base class, which other components could inherit from:This would essentially forward the props down the chain until we hit a "concrete" built-in component. Any arguments against making a
root
ref available by default?The text was updated successfully, but these errors were encountered: