Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the
renderProp
API as described in #1863 (comment).This is merely a suggestion at the moment and I'm happy to close it again if we settle on another approach or even keep the current one.
The motivation for "returning a function" is that the arguments to enzyme's
renderProp
won't get mixed with the arguments to the render prop function itself. This allows us to eventually add more options (like context) which we can apply to the newly created wrapper.An example usage (formatted with Prettier) would look like this:
Sidenote
At this point, one might wonder what the advantage of
wrapper.find(Foo).renderProp('render')()
overwrapper.find(Foo).prop('render')()
is, and that's a fair question.When using
renderProp
, the render props' return value gets nested into a new wrapper which enables this convenient chaining shown above - whereaswrapper.find(Foo).prop('render')()
simply returns the React element without an enzyme wrapper. More about this is hinted at in this article.