Added two more deobfuscator options, refactored options and more #81
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.
Made deobfuscator options globally available via
Context
classRefactored how deobfuscator options where stored. I splitted it into
DeobfuscatorOptions
andDeobfuscatorOptions.Builder
classes. This allowed make it available inContext
class and be able to use them outsidedeobfuscator-impl
module.Added two options:
suppressErrors
andverifyBytecode
suppressErrors
(default:false
, but set totrue
inBootstrap
) - From now when some transformer fail, then it stops further execution. This behaviour is required for tests to fail if some transformer will fail to run. Using this option, we can prevent this behaviour and allow further execution.verifyBytecode
(default:false
) - This option verifies bytecode after every transformer run. Useful when debugging which transformer broke bytecode and what exacly.Other changes