aboutsummaryrefslogtreecommitdiff
path: root/gnu/packages/java-xml.scm
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/packages/java-xml.scm')
0 files changed, 0 insertions, 0 deletions
uotedkzc Fixes: #1247 Fix --mangle-props and --name-cache inconsistency. AST_Dot and AST_Sub properties are now mangled by --mangle-props without regard to being used in an assignment statement. Note: if --mangle-props is used then *all* javascript files used must be uglified with the same mangle options. Fix the ignore_quoted=true mangle option, also known as `--mangle-props=unquoted`. If a given property is quoted anywhere it will not be mangled in any quoted or non-quoted context. 2016-06-19Respect quote style in object literalsShrey Banga The option added in fbbaa42ee55a7f753f7cab9b1a905ccf73cf26d5 wasn't being respected inside object literals, so quoted property names would still be stripped out with this option. This is mostly a corner-case, but useful when the output is passed to something like the Closure compiler, where quoted property names can be used to prevent mangling. 2015-08-05Fix mangling of property names which overwrite unmangleable propertiesRichard van Velzen Fixes #747. 2015-06-09Add --mangle-regex optionJoao Carlos 2015-05-13fix again reserved propsMihai Bazon 2015-05-07Make reserved names take priority over the name cacheMihai Bazon 2015-04-22If name_cache is specified, do rename cached propertiesMihai Bazon (even if --mangle-props is not there) 2015-04-10Use the `before` visitor in mangle propsMihai Bazon (works around a bug in our tree walker which, while cloning nodes, breaks references between labeled statements and break/continue labels) 2015-03-16Fix prop manglingMihai Bazon Even if not “defined”, do mangle if name exists in the cache. 2015-03-14Add property name manglerMihai Bazon We only touch properties that are present in an object literal, or which are assigned to. Example: x = { foo: 1 }; x.bar = 2; x["baz"] = 3; x[cond ? "qwe" : "asd"] = 4; console.log(x.stuff); The names "foo", "bar", "baz", "qwe" and "asd" will be mangled, and the resulting mangled names will be used for the same properties throughout the code. The "stuff" will not be, since it's just referenced but never assigned to. This *will* break most of the code out there, but could work on carefully written code: do not use eval, do not define methods or properties by walking an array of names, etc. Also, a comprehensive list of exclusions needs to be passed, to avoid mangling properties that are standard in JavaScript, DOM, used in external libraries etc.