-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Update ReactCoroutine-test to only use public API #11338
Conversation
In this case, these tests are currently testing apis that haven't been exposed publicly yet, so there isn't currently an actual public api to be used. For now, expose `createCoroutine` and `createYield` through the `ReactNoop` renderer, which is already used for testing (as per @gaearon's suggestion). When these apis are exposed publicly, these tests can be updated using that api. Part of #11299
@sebmarkbage Would you be okay with just exposing these as |
The more I thought about this the more sense it seemed to make to extract it to a separate package instead of tacking those onto the Noop reconciler. I was in the middle of a packaging change anyway the past few days so I went ahead and did it in #11364. So unfortunately I'm closing this. But I really appreciate that you sent this PR! It's what pushed me over the edge to actually address this :-) |
ah cool, no worries! :) |
In this case, these tests are currently testing apis that haven't been exposed
publicly yet, so there isn't currently an actually public api to be used.
For now, expose
createCoroutine
andcreateYield
throughReactNoop
renderer, which is already used for testing (as per @gaearon's suggestion).
When these apis are exposed publicly, these tests can be updated using that api.
Part of #11299