Remove InternalApi from Watchdog, and add InternalApi to FixedWatchdogProvider #881
Conversation
Codecov Report
@@ Coverage Diff @@
## master #881 +/- ##
=========================================
Coverage 78.63% 78.63%
Complexity 1163 1163
=========================================
Files 203 203
Lines 5143 5143
Branches 413 413
=========================================
Hits 4044 4044
Misses 925 925
Partials 174 174
Continue to review full report at Codecov.
|
@@ -59,7 +58,6 @@ | |||
* had no outstanding demand. Duration.ZERO disables the timeout. | |||
* </ul> | |||
*/ | |||
@InternalApi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EndUsers should really not be setting Watchdogs directly. However if you insist on continuing on with this PR, at least mark this as BetaApi, since its api was never reviewed for public consumption and please mark it as final so that users don't try to extend it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But isn't marking a class as @BetaApi
considered breaking change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding is that since its marked InternalOnly, we are allowed to change this class in any way we see fit.
I can't figure out why Java 7 tests failed... @vam-google passing this to you. |
Closing as obsolete (implemented as parto of #1119) |
Fix #829