-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Better documentation about async argument #440
Comments
Here's a good answer from Jake: https://www.reddit.com/r/androiddev/comments/97u44h/rxandroids_new_async_api/e4blnkd/
|
How often are you calling this API? It should be once for the whole app. We couldn't make it the default, but it would have been if we could. |
@hzsweers 🔍 🕵️ the Medium post is also slightly confusing:
In the code samples, |
Ahh ok. I misread the blog post. I assumed that we had to decide to supply this to every instance of:
|
No you should never do that. Schedulers are long-lived instances–ideally singletons. |
I guess there are now enough conversations floating around here, reddit, and SO that it should be clear when/how to use this. |
I like that the
async
argument got added in #416. But even after reading https://medium.com/@sweers/rxandroids-new-async-api-4ab5b3ad3e93 I still don't know when to use it. This got raised on the original issue: #228 (comment) Right now I'm inclined to to just slap it on every call. Any guidance in either readme or javadoc would be much appreciated.The text was updated successfully, but these errors were encountered: