To increase performance and prevent possible runtime errors `transfor… #951
Conversation
…mObjectKeys` option now completely ignores objects with `CallExpression` nodes
…mObjectKeys` option now completely ignores objects with `NewExpression` nodes
|
I think you need to remove the "?." optional chaining as your using node v12 I think. You can probably simplify the isTrue function to simply false and still get the same behaviour. |
Yeah, just forgot to reset |
| }); | ||
|
|
||
| it('shouldn ignore object expression if it contains a call expression and the previous property value is object expression', () => { | ||
| assert.match(obfuscatedCode, regExp); |
There was a problem hiding this comment.
Just curious but would it be easier to actually execute the obfuscated code rather than test via regExp? I guess you have to do both.. Its just regular expression is so hard to follow I'm definitely lost :).
There was a problem hiding this comment.
Sometimes i need to evaluate obfuscated code (to be sure that it runs fine), but in this cases i want to be sure that obfuscated code looks right, so - RegExp
…mObjectKeys
option now completely ignores objects withCallExpression` nodes