Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Thenable::none #36

Closed
paulyoung opened this issue Mar 24, 2015 · 2 comments
Closed

Thenable::none #36

paulyoung opened this issue Mar 24, 2015 · 2 comments
Labels
enhancement

Comments

@paulyoung
Copy link
Contributor

This would be the opposite of Thenable::all in that it rejects if any of the items fulfill and succeeds if any item rejects.
@bergie
Copy link
Contributor

bergie commented Mar 24, 2015

Quick workaround would be to wrap each task into a subtree with a then abort, else send data. But thenable.none wouldn't be that hard to do either. I'd appreciate a spec for it first :-)

paulyoung added a commit that referenced this issue Mar 24, 2015
@paulyoung
Add specs for Thenable::none composite.
3fd46ea 
* Relates to #36.
@paulyoung
Copy link
Contributor Author

@bergie added some simple specs.

@bergie bergie closed this as completed in 124eca4 Mar 25, 2015
paulyoung added a commit that referenced this issue May 18, 2015
@paulyoung
Add specs for Thenable::none composite.
73e164c 
* Relates to #36.
bergie added a commit that referenced this issue May 18, 2015
@bergie
Implement thenable.none, fixes #36
e7720a1
paulyoung added a commit that referenced this issue May 18, 2015
@paulyoung
Add specs for Thenable::none composite.
1642b15 
* Relates to #36.
bergie added a commit that referenced this issue May 18, 2015
@bergie
Implement thenable.none, fixes #36
8c63670
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bergie @paulyoung