ShrinkWrap
  1. ShrinkWrap
  2. SHRINKWRAP-215

Do not expose implementation-specific InputStreams from the Importer/Exporter APIs

    Details

    • Type: Task Task
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0-alpha-12
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      We should accept Files and InputStreams, not any implementation-specific types in these APIs.

      For instance: importFrom(ZipInputStream) is leaking out the internals of how we modify these contents. Just take in a generic instream and let our impls do all necessary wrapping.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Andrew Rubinger
            Reporter:
            Andrew Rubinger
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: