Ben Lickly
Ben Lickly
Ah, good point. Thanks for the workaround.
Sure, I know that the ParserConfig.properties file is a way that we blacklist certain names from renaming: https://github.com/google/closure-compiler/blob/master/src/com/google/javascript/jscomp/parsing/ParserConfig.properties so that might be a way to workaround the issue. But I...
Good questions. I wondered the same thing. It looks like the code that makes sure to skip keywords as generated names (in both the Random and Default name generators) is...
I was able to reproduce this, and minimize the example a bit more: ``` function __webpack_modules__123() { function myFunction() { console.log("hello"); } return { myFunction: function() { return myFunction; }...
Oops, thanks for catching that. It still does look like one of the peephole passes is breaking the code. I think that the issue is that when determining whether `myModule.myFuntion()`...
The type-signature of Array.prototype.reduce is defined in the externs, at https://github.com/google/closure-compiler/blob/master/externs/es3.js#L704 It seems like the correct type for reduce would be for the callback first argument and the initial value...
This is not something that we are currently prioritizing.
That makes sense to me. I think the thrust of my issue is that ID users should have *some* way to turn on "stylistic" linting without needing to make the...