-
Notifications
You must be signed in to change notification settings - Fork 40
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
Tracking 1.1 #74
Comments
Hey, are you still planning on releasing 1.0?, let me know If I can help with some task |
Still intend to, not been doing any React component testing lately so it's slipped a bit, Either extra test coverage, porting older tests over to the new test style or implementing the new APIs would be useful |
Given your time constraints if I may be so bold as to suggest a few things:
|
Yeah, implementing those is all that's really missing for a beta release. I think I published what's here so far as a Its been really sunny here lately so I've not been coding as much! |
I've just added Will try not to let this slip much more ☀️ |
Awesome. Appreciate your hard work. |
Braindump of actions, will expand on these as I go.
subTreeLike
has been renamed tosubTree
everySubTreeLike
has been renamed toeverySubTree
subTree
has been removed,exact
can be used to get this behaviour back, but I don't recommend you do.subTreeLike
has been removed,exact
can be used to get this behaviour back, but I don't recommend you do.findNode
, usesubTree
insteadtextIn
, usesubTree().text()
insteadfillField
, usesubTree().props.onChange
insteadfindComponent
, usesubTree()
insteadfindComponentLike
, usesubTree()
insteadtoString()
no-longer expands child components Better tostring output #26reRender()
now takes props instead of a ReactElement.master
branchbeta
to npmThe text was updated successfully, but these errors were encountered: