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

Don't require passing an Option to an asynchronous query callback #61

Closed
ghost opened this issue Jul 4, 2016 · 1 comment
Closed

Don't require passing an Option to an asynchronous query callback #61

ghost opened this issue Jul 4, 2016 · 1 comment
Labels
enhancement New feature or request

Comments

@ghost
Copy link

ghost commented Jul 4, 2016

Since we can infer from the invoked callback/errback whether the fetch succeeded or not, we shouldn't require the callback type to be Option[Identity] => Unit but Identity => Unit.
@ghost ghost added the enhancement New feature or request label Jul 4, 2016
@ghost
Copy link
Author

ghost commented Nov 21, 2016

Required to be able to signal missing identities from async queries, closing this.

@ghost ghost closed this as completed Nov 21, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants