Closed pocesar closed 7 years ago
+1, i'm waiting for opinion on https://github.com/LearnBoost/expect.js/issues/98 , otherwise in 24 hours I'll decide on my own and begin to contact other PR authors to call for a take over.
+1
Please leave a link here if there is any kind of organized take-over on this. I'm apprehensive about using expect.js because of lack of maintenance, but there aren't many libraries like this that run on ie8.
@HarryPehkonen true! the only reason I don't use chai is because it only support IE9+
https://github.com/truongsinh/expect I have been lately working on this fork. Please read "read me" and history.md for more info, as there are breaking changes. I will now start asking for npm and bower package name.
What are the main bugs you'd like to see fixed? We use this for socket.io and engine.io and never run into issues.
@guille are you asking me or others? For others, as said, this codebase has been abandoned for 8 months, until hours ago (thanks for getting back after my email, though), however there are still open 14 PRs, most of which are fixes, with test case provided. For I myself, I found it is hard to extend expect
, because of its structure, you can take a look @ my fork's Readme.
Anyway, I'm happy that you come back.
@guille ping, any write up? You said in another issue that you believed expect.js is no longer the solution. However, I and many people here find this the only one supporting IE8 (by scarifying the extendability, like of chaijs's, but I rewrite it in my fork).
is this package still maintained?
if you're looking for maintainers, please add that to the readme. if not, please add it to the readme.
I forked this and created Expecting.js which I intend to maintain.
No PRs being accepted, no bugs being fixed, what gives? Maybe someone should take this over?