-
Notifications
You must be signed in to change notification settings - Fork 165
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
Maintain a list of conformant implementations #59
Comments
then/promise is now just being referred to as promise. I'm a 👍 for this list, it's a good incentive for people to make their libraries comply, and it helps us find libraries we can use. |
+1 At some point, we may want to extend it to be a table with a column for each "add-on" spec, like progress, etc. and possibly a column for notes, etc. I just tagged avow 1.0.0, so we can specify avow >= 1.0.0, and when.js 2.0.0 will be the first release that is fully compliant. Until then, it'll be compliant in all ways except async resolutions. |
Thank you guys for the effort of making promises a defacto standard! |
I'd like to submit https://github.com/CodeCatalyst/promise.coffee to the list. |
And @juandopazo and I are working on YUI 3. |
On a related note it may be helpful to name and shame non-conforming promises that are seen in the wild along with the relevant issue asking them to become compliant. That way we could all chime in in favour of proper compliance. At the moment the many non-conforming promise implementations are doing a lot to give promises a bad reputation. |
I think it'd be awesome to have a list of conformant implementations we can point to. Maybe with a one-sentence description of each by the authors. The requirement would be that they pass the test suite.
This would just be another doc in the repo, and could include details on how to put the logo in your README as per #57. Then we'd point people to the gh-pages version.
Right now I believe we have:
The text was updated successfully, but these errors were encountered: