This repository has been archived by the owner on Mar 18, 2019. It is now read-only.
Don't repeat class and version mismatch warnings #157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to make it easier to wade through all of the warnings I'm getting!
Also a fix for something I was hitting with bundle-extract: if you run disunity from the same directory as the bundle then there's no parent path in a default output dir so the 'getParent().resolve' didn't work.
Thanks! I will look into updating the types.dat too; what would you suggest, e.g. get the Unity Labs demo and all of the standard packages for a specific Unity version and try and import types from that data?