Remove usages of deprecated APIs #134
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While perusing the source tree, I noticed some deprecated methods:
User.get(java.lang.String)states: "This method is deprecated, because it causes unexpectedUsercreation by API usage code and causes performance degradation of used to retrieve users by ID. UsegetById(java.lang.String, boolean)when you know you have an ID.edu.umd.cs.findbugs.annotations.SuppressWarningsstates: "Was used to suppress FindBugs warnings but generates name conflicts withSuppressWarnings".Accordingly, I replaced any calls to
User.get(java.lang.Stringwith calls toUser.getById(java.lang.String, boolean, and I replaced any usages ofedu.umd.cs.findbugs.annotations.SuppressWarningswith usages ofedu.umd.cs.findbugs.annotations.SuppressFBWarnings.