-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Upgrade path #638
Comments
Are there any updates related to this thread? I opened a new pr for mocha 9 |
Not sure, @rwjblue and I came up with a plan where ember-mocha would take a completely different approach than what it has up to this point, but I feel the change is too drastic. I feel like now that Ember has dropped support for IE we can use the Proxy approach that I originally developed, but again I'm not a maintainer and for our Ember project at our company we continue to use my fork. |
@yads I am all ears... I would love to see this package more maintained... |
Best I can offer at the moment is my fork :) |
@yads would you be happy to take ownership of this? |
We've recently moved off of mocha and I also tried to update my fork to Ember 4.x and could not get the tests to actually work. Unfortunately I'm no longer in a position to take ownership of this package :( |
No problem! Thanks for what you have done. |
I've been working on updating this repository with several updates:
These are all updates I've made in my fork, specifically the ember-mocha-compat branch https://github.com/yads/ember-mocha/tree/ember-mocha-compat
The first 2 features are handled by #633, once these are merged I can submit another PR for the UI test page.
The text was updated successfully, but these errors were encountered: