-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add predicate for the '.withProps' method #194
Comments
Hi @ChrisLane, Thank you for sharing this idea with us. |
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open. |
Bump |
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open. |
Bump |
I would like a new version of
withProps
that is able to accept a function as an argument that determines whether a component should be returned.Example use case:
We pass Immutable.js objects to component properties and want to match against their values.
Currently, I'm not aware of a clean way that we can do this but with the above proposal, we could hopefully do something like this:
The text was updated successfully, but these errors were encountered: