Deprecate RPC superclass initializers #1262
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
* So that they won’t appear on every RPC initializer in autocomplete and confuse developers
joeljfischer
added
the
best practice
joeljfischer
changed the title
NicoleYarroch
suggested changes
May 16, 2019
NicoleYarroch
approved these changes
May 17, 2019
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.
Fixes #1204
This PR is ready for review.
Risk
This PR makes minor API changes.
Testing Plan
Unit testing and smoke testing
Summary
This PR deprecates RPC superclass initializers so that they are not clearly available for developers to use, which can be confusing. Ideally, these methods would be "protected" methods and not be available at all, but because they were publicly available, they have to be deprecated until the next major version.
Changelog
Bug Fixes
Tasks Remaining:
CLA