As justification for why we should not have this type of logging, it would scale up to about 13K LOC, 1800 Strings, and 36K (after pro-guarding - in the case of the demo app) if we did it through the whole code base*. It makes the code messier to read, and in most cases doesn't add significant value. Note: I left the Scheduler logging because it logs interactions with some awkward library components outside of ExoPlayer, so is perhaps a bit more justified. * This is a bit unfair since realistically we wouldn't ever add lots of logging into trivial classes. But I think it is fair to say that the deltas would be non-negligible. PiperOrigin-RevId: 246181421
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| CacheAsserts.java | Loading commit data... | |
| DefaultRenderersFactoryAsserts.java | Loading commit data... | |
| FakeMediaChunk.java | Loading commit data... | |
| FakeMediaChunkIterator.java | Loading commit data... | |
| FakeMediaClockRenderer.java | Loading commit data... | |
| FakeShuffleOrder.java | Loading commit data... | |
| FakeTrackSelection.java | Loading commit data... | |
| FakeTrackSelector.java | Loading commit data... | |
| MediaPeriodAsserts.java | Loading commit data... | |
| MediaSourceTestRunner.java | Loading commit data... | |
| OggTestData.java | Loading commit data... | |
| RobolectricUtil.java | Loading commit data... | |
| StubExoPlayer.java | Loading commit data... | |
| TestDownloadManagerListener.java | Loading commit data... | |
| TimelineAsserts.java | Loading commit data... |