Comments (4)
Its a problem because if using promises as a return value for generic reusable functions, one should always know which methods can be used. And so if .done is not in spec, nobody should use this implementation for such case.
from promise.
We have "core.js" which is a bare bones Promises/A+ implementation. index.js then contains extensions to that and is a super-set of the extensions provided by ES6 promises. https://www.promisejs.org/ has recently been updated to make clear that promise.done
is non-standard. .done()
is also implemented by the majority of popular promise libraries. This library could possibly use improved documentation though.
Other methods to be aware of:
Promise.from
and Promise.cast
are also unlikely to be part of the ES6 standard and will likely be deprecated from this library at some point. Promise.cast
was briefly in the spec which is why it got added here.
Promise.denodeify
and Promise.prototype.nodeify
are not and will not ever be part of the ES6 standard, but they are going to remain in this library as they are necessarily for the library to be practical/useful in node.js
from promise.
Thanks. This is something one should read in the first place...
from promise.
These functions are marked with "Non Standard" in the README, closing.
from promise.
Related Issues (20)
- Promise do not change to "resolve" mode when calling the function again. HOT 4
- can Promise.resolve replace by code like this? HOT 2
- Add an additional method HOT 3
- promise pending HOT 1
- Discuss ways to avoid `new Function` in denodeify HOT 1
- Why promise. then is faster than setTimeout HOT 1
- who can tell me that what is the meaning of the code? HOT 2
- promise.race() missing from the API description in README HOT 4
- Promise.race resolves the combined Promise multiple times, which emits an error/warning event in node HOT 1
- Questions regarding unhandled rejections HOT 4
- Difference with native Promise HOT 2
- Promise.prototype.finally is not aligned with the most current spec draft HOT 1
- if (fn === noop) return; Can't judge correctly HOT 1
- Catch works earlier if I pass reject as second callback HOT 1
- code refactor. use new.target to detect if promise is called with new instead of this check HOT 1
- How can I build a setimmediate flavor that is not uglified? HOT 1
- optifine bugs HOT 1
- It's difference between native and shim HOT 1
- Promise.allSettled ? HOT 2
- [BUG]Why this promise execute queue is not same with v8 Promise。 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from promise.