-
Notifications
You must be signed in to change notification settings - Fork 24
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
Is project going to support preact 10? #92
Comments
Hello, @gnarf, @mzgoddard can you please comment on the Preact 10 support? |
Thanks!) |
I apologize for the late reaction. I'd like to make a PR, but at the moment I'm not sure if it would ever be accepted. However, I quite like preact-render-spy for smaller projects over a much bigger enzyme. If there is no reaction from maintainers, maybe we can join forces elsewhere. I've also noticed some meaningful commits from @soerenvullriede2101. |
We used preact-render-spy for a small project, with the update to v10 we wanted to use Fragments, so we updated the fork of @shelacek and fixed some tests. But there are still a bunch of failing tests, especially the https://github.com/mzgoddard/preact-render-spy/blob/master/src/shared-render.test.js . It seems like the contains function etc. does not work anymore. I could create a PR for the stuff we did, but this project seems kinda abandoned. |
Any update on this? |
I guess its dead, would recommend to switch to something else if possible. I tried to fix a few things to make it kind of work again, but it feels kinda hacky. PS: Im @soerenvullriede2101 this is my private account |
thanks for the info, FYI: I checked out a new prect-cli typescript project and it is using enzyme now. |
We migrated towards preact-testing-library, forem/forem#8224 |
No description provided.
The text was updated successfully, but these errors were encountered: