Andreas Källberg
Andreas Källberg
@sanex3339 Oh, I only now made the connection that you wrote obfuscator.io, so updating the deobfuscators would mean more work for you.
> > I can break eval in the future btw, because there is a way to know if we inside an eval call. > > funny they use your tool...
Oh, cool! This code checks that the code hasn't been pretty-printed. ``` var noPrettyPrintingPls = function(){return 'newState';}; /\w+ *\(\) *\{\w+ *['|"].+['|"];? *\}/.test(noPrettyPrintingPls.toString()) ``` Sneaky!
Now that #130 is merged, this can probably be closed.
@geekosaur Aha, that's disappointing. So I assume there is no simple workaround I can do either? Thanks for the quick answer!
Should I close this as a duplicate of that issue then?
Regarding moving to using (what was) newly added features in `base`: I think the standard solution for this is to use [`base-compat`](https://hackage.haskell.org/package/base-compat), which has backported all the new stuff for...
What does index sensitive mean?
The workaround I've used is to transform the value with this function prior to parsing, so that it can work with any parser that can accept `null` (instead of just...
Maybe we could add a new option called `missingAsNull` or something, which would interpret any missing field as null before sending it off to the next sub-parser instead of (as...