Skip to content
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.

Access to non-standard cap file components #11

Open
jmrgibson opened this issue Oct 17, 2018 · 1 comment
Open

Access to non-standard cap file components #11

jmrgibson opened this issue Oct 17, 2018 · 1 comment

Comments

@jmrgibson
Copy link

Firstly, thanks for all the great work on this so far. Just having a sane implementation of GP stuff has been a great reference when compared to the GP docs.

Could we change the access level of "entries" in the CAPFile class, or provide some other method of getting it? We have some other legacy systems that sign our cap files and use a different format than supported (specifically, it uses "meta-inf" in lowercase.., among other silly things).

I come from python land so I'm used to just having access to anything I need, but could we make the implementation a little more flexible here?

I could either

  1. Make the entries type protected so that I can subclass it and implement the DAP component lookup for our specific system there
  2. Make a public getZipFileComponent method that gets any arbitrary component out of the zip, then deal with it there

I'd be happy to implement, submit the PR, and bump the version in GlobalPlatofrm

@martinpaljak
Copy link
Owner

martinpaljak commented Oct 17, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants