Suppress deprecation warnings for radarSearchQuery #302
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I run
./gradlew test
, there are deprecation warnings becausePlacesApiTest
callsPlacesApi.radarSearchQuery
, which is deprecated.When I enable verbose
-Xlint:deprecated
, I get this.Because this is commented as still working until June 2018, I assume that it's intentional to keep the tests for it in place until the feature is actually turned off and it is removed from the google-maps-services-java API.
This PR suppresses those deprecation warnings, leaving the tests in place. This results in cleaner output for developers running the tests.
This PR also enables verbose output for deprecation warnings to make diagnosing them easier. I think this is a good idea because aside from the
radarSearchQuery
warnings, which are now handled in this PR, there are no deprecation warnings, so it won't end up spamming people who run the build. And IMHO this is the right approach to use for tracking down deprecated method calls and either fixing them up or putting warning suppressions on them.