-
Notifications
You must be signed in to change notification settings - Fork 107
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
Adapters are not called with promises, are they? #65
Comments
It sounds like a bug in the test cases, hmm. What tests in particular trigger this? Note that we do pass promises to |
The 2.3.3 testcase for
with its various
That's OK, the spec expects nesting behaviour for that anyway :-) |
+1 on this. I'm facing the same problem. |
https://saucelabs.com/jobs/7065f290c8aa403fb50c0f677d98b9e9 I meet the same problem on android 4.4 default browser. but other browsers all pass. |
The adapters section of the readme says:
I'm not sure whether this is wrong, outdated or uses outdated terminology after #39 ?
The implementation that I'm currently testing does not (yet?) have a
Promise
constructor with aresolve
callback, it only offers afulfill
callback which accepts any value and does not[[resolve]]
its arguments recursively (yes, I'm allowing algebraic nesting of promises). I also did pass the monadicPromise.of
foradapter.resolve
.However, this has bitten me heavily, and it took me some time to figure out that
deferred.resolve
is indeed called a few times with one of myPromise
s. Is this a bug in the test cases? An error in the documentation? Or did I just misunderstand that sentence?The text was updated successfully, but these errors were encountered: