1. 17 Feb, 2020 13 commits
  2. 13 Feb, 2020 20 commits
  3. 11 Feb, 2020 7 commits
    • Fix demo app download notification · 7a849e11
      PiperOrigin-RevId: 294503035
      olly committed
    • Format: Move language into common fields section · 147f70bf
      Language is already applicable to image formats as well.
      It can also apply to video formats. For example when the
      video contains burnt in subtitles. Also, some animation
      studios produce multiple variants of animations, in which
      text within the scene itself (e.g., a signpost) is
      replaced to be language specific.
      
      PiperOrigin-RevId: 294500227
      olly committed
    • DataSpec: Make DataSpecTest more useful · 39c65c65
      - Replace tests specific to HTTP request headers with tests that
        more generally test constructor correctness.
      - Add test specifically around the constructor that infers the
        HTTP method from postBody, since that's a non-trivial bit of
        constructor logic.
      
      Note: In general, I'm not sure this type of test (i.e., testing a
      bit of trivial copying through a constructor) is worth the cost
      of writing and maintaining them. That said, checking the new
      uriPositionOffset is calculated correctly is non-trivial, as is
      the HTTP method inference, so keeping them for now.
      PiperOrigin-RevId: 294488684
      olly committed
    • Replace DataSpec.absoluteStreamPosition with uriPositionOffset · 829282fa
      This is a preliminary step toward adding a DataSpec.Builder,
      which is needed for sanity when adding DataSpec.customData.
      
      The existing absoluteStreamPosition field is very error prone,
      because anyone using a Builder to adjust the request position
      will need to remember to adjust two values:
      
      dataSpec
          .buildUpon()
          .setAbsoluteStreamPosition(x)
          .setPosition(x)
          .build();
      
      Furthermore, the difference between position and
      absoluteStreamPosition is irrelevant in nearly all cases. In
      the core library, the difference is only relevant when initializing
      AES encryption/decryption to write/read cache files.
      
      Replacing absoluteStreamPosition with uriPositionOffset will
      simplify the code block above to:
      
      dataSpec
          .buildUpon()
          .setPosition(x)
          .build();
      
      PiperOrigin-RevId: 294485644
      olly committed
    • Write extractor dumps to testdata · 58bc460b
      PiperOrigin-RevId: 294465827
      kimvde committed
    • Merge pull request #6949 from DolbyLaboratories:dev-v2-assets · fed0acc2
      PiperOrigin-RevId: 294441610
      kim-vde committed
    • Fix JavaDoc · f59755f5
      Replace Thread with thread on documentation.
      
      PiperOrigin-RevId: 294401357
      christosts committed