Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Apply TypeScript to Fragment & LevelKey #2107

Merged
merged 12 commits into from Feb 5, 2019
Merged

Apply TypeScript to Fragment & LevelKey #2107

merged 12 commits into from Feb 5, 2019

Commits on Jan 29, 2019

  1. Update Fragment and LevelKey to typescript.

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    64f13c4 View commit details
    Browse the repository at this point in the history

  2. Update usage of Fragment and LevelKey.

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    af437da View commit details
    Browse the repository at this point in the history

  3. Don't pass prevFrag into EXT-X-MAP handling.

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    40e81b8 View commit details
    Browse the repository at this point in the history

  4. Add tests for parsing byte range as seperate call.

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    2a80ff2 View commit details
    Browse the repository at this point in the history

  5. Only parse byte range if it exists.

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    b37a351 View commit details
    Browse the repository at this point in the history

  6. Apply suggestions from code review 

    Co-Authored-By: itsjamie <1956521+itsjamie@users.noreply.github.com>
    @tjenkinson @itsjamie
    tjenkinson and itsjamie committed Jan 29, 2019
    Copy the full SHA
    a742c30 View commit details
    Browse the repository at this point in the history

  7. Review changes. 

    parseByteRange -> setByteRange
- removed it returning the parsed value since its usage was like a setter.
    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    2e2cb12 View commit details
    Browse the repository at this point in the history

  8. Review comments pt.2

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    c8b0048 View commit details
    Browse the repository at this point in the history

  9. Change tests to call setByteRange

    @itsjamie
    itsjamie committed Jan 29, 2019
    Copy the full SHA
    150d1e6 View commit details
    Browse the repository at this point in the history

Commits on Jan 30, 2019

  1. Explicit handling of 'initSegment' conversion for bitwise operation.

    @itsjamie
    itsjamie committed Jan 30, 2019
    Copy the full SHA
    9329b55 View commit details
    Browse the repository at this point in the history

  2. Add handling for AES-128 encrypted initialization segments needing IV.

    @itsjamie
    itsjamie committed Jan 30, 2019
    Copy the full SHA
    3902e1f View commit details
    Browse the repository at this point in the history

Commits on Feb 2, 2019

  1. Change IV handling for initSegments to just log a warning.

    @itsjamie
    itsjamie committed Feb 2, 2019
    Copy the full SHA
    a31f1be View commit details
    Browse the repository at this point in the history