-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for expo-image or other components #35
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
I'd be interested in this too! |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days. |
This issue was closed because it has been stalled for 15 days with no activity. |
Is your feature request related to a problem? Please describe.
expo-image is beginning to take over
<Image/>
component from react native.Describe the solution you'd like
Instead of making a new exported component maybe we could implement a createZoomComponent, which would make any kind of component zoomable, with your current implementation.
Then you could go:
Describe alternatives you've considered
Another way would be to implement a
<ZoomableView>{children}</ZoomableView>
kind of component that could just make any child component zoomable.The text was updated successfully, but these errors were encountered: