-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update Javadoc for ShadowContentResolver about deprecation notices #8874
Labels
Comments
Hi, I would like to work on this Issue @hoisie can you assign this to me, thanks |
@shashankiitbhu I assign this task to you. Please prepare a PR for it. Thanks. |
@utzcoz sure |
HI @utzcoz , should all the |
@shashankiitbhu yeah that is on the right track. Something like this could be better: /**
* @deprecated This method affects all calls, and does not work with {@link
* android.content.ContentResolver#acquireContentProviderClient}. Instead, use
* {@link org.robolectric.Robolectric#setupContentProvider(Class, String)} to
* install a test-specific ContentProvider that can return any Cursor.
*/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In ShadowContentResolver there are a lot of
@Deprecated
methods. However, there are no suggestions to what should be used instead. This has caused a lot of confusion. The Javadoc should be updated with better information.The alternative to ShadowContentResolver is creating fake ContentProviders and registering them using
Robolectric.setupContentProvider
orContentProviderController
.The text was updated successfully, but these errors were encountered: