You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be a complete nightmare, but would be a great help in making these libraries more user friendly. The upcoming v4 release fixes all of the weird quirks, so it should be ready enough to use...
A lot of the fixes are smallish syntax things, i.e.
Would also need to add a special case for the maid accepting promises, as these don't implement a .destroy method. I've been slowly converting libraries as I use them, would PRs be accepted on some separate branch?
The text was updated successfully, but these errors were encountered:
I'm planning on providing promise-compatibility with eryn's promises, and then maybe eventually switching over to eryn promises full time.
This will probably need to go in phases. First, adding an appropriate API surface that accepts andThen callbacks, and a suite of unit tests. Then, adjusting API calls around the codebase to use Eryn's promises layering, and then finally, maybe transparently switching out certain packages promises.
This could be a complete nightmare, but would be a great help in making these libraries more user friendly. The upcoming v4 release fixes all of the weird quirks, so it should be ready enough to use...
A lot of the fixes are smallish syntax things, i.e.
Would also need to add a special case for the maid accepting promises, as these don't implement a
.destroy
method. I've been slowly converting libraries as I use them, would PRs be accepted on some separate branch?The text was updated successfully, but these errors were encountered: