Conversation
Fixed so it works on windows, switched to adm-zip for decompression, and added progress for progress monitoring when downloading Build Tools. Also fixed a minor bug in the parser where it wasn't looking for C: symbols and skipping them. Really it should just skip any unknown symbols.
|
Cool! Do you have an example of such a missing string that we can add as a test case? |
|
Here is a cobbled together section, sorry I had to cut a few different dumps together to keep out company IP information: That C: ".9\n" is the line I've seen. No clue what its for. |
|
Oh and sorry about the catch(e)'s throwing Travis CI off, wouldn't have thought you would be using JSHint with IE mode :) |
|
IE mode? |
|
The error from Travis CI is "[L141:C26] W002: Value of 'e' may be overwritten in IE." based on my try/catch blocks only using catch(e). There should be a flag on JSHint that turns off IE only warnings, sorry don't use JSHint so I don't know what the flag is, that should be safe to turn off since apk-parser really couldn't be used in a browser. |
|
I just noticed that there isn't any I don't really care about IE compatibility for Node.JS code, I do care about consistent code style :-) |
|
I just added a JSHint configuration. It should cause the linting to behave more reasonably. From looking at your diff, you'll probably get a ton of new errors and warnings, mostly about whitespace. Sorry about that, but you'll have to fix it. The patch is currently a mix of different styles and that's just plain ugly. For instance, there's both I'd love to merge this (good additions!), but we need to step up the code quality a bit first. |
Fixed so it works on windows, switched to adm-zip for decompression, and
added progress for progress monitoring when downloading Build Tools.
Also fixed a minor bug in the parser where it wasn't looking for C:
symbols and skipping them. Really it should just skip any unknown
symbols.