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
Fix 198 prop type and docs #199
Conversation
The docs fail to mention that whatever component is supplied to the `component` prop must support an `onPress` callback prop in order to function.
Using a custom `component` prop only works when the specified custom component type itself accepts an `onPress` callback prop.
Added language hints to the fenced code blocks missing them to introduce syntax coloring when Github renders them. Also fixed some parse errors in JS blocks, and small whitespace tweaks.
Hey gang. I've opened up a support ticket, too, but I'd really like to get rid of that incorrect proptype warning at the bottom of my simulator. It's not a good look for our demos 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Prometheas, thank you so much for putting out this PR!
I changed some of the README.md around the token field, but otherwise LGTM
Any guidance as to when this fix will go out to npm? |
Addresses issue #198.