Databases
StackOverflow2013
Postsdbo
POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
    primarykey
    data
    text
    <p>This question follows: <a href="https://stackoverflow.com/questions/8196243/why-does-closure-compiler-rename-properties-of-an-extern-type/8198809#8198809">Why does Closure compiler rename properties of an extern type?</a> John's answer to that question brings up this second question.</p> <p>If I declare the extern type as suggested:</p> <pre><code>/** @interface */ function SpanishNoun() {} /** @type {string} */ SpanishNoun.prototype.english; /** @type {string} */ SpanishNoun.prototype.spanish; </code></pre> <p>then Javascript like:</p> <pre><code>/** * @param {SpanishNoun} n */ exp.foo = function (n) { console.log(n.english, n.spanish, n['english'], n['spanish']); } </code></pre> <p>will compile, as desired, to:</p> <pre><code>function(a){console.log(a.english,a.spanish,a.english,a.spanish)}; </code></pre> <p>The properties are not renamed as usual. Without the extern declaration, the compiled code would look like:</p> <pre><code>function(a){console.log(a.a,a.c,a.english,a.spanish) </code></pre> <p>That's all good. The problem is that the compiler has stopped renaming 'english' and 'spanish' in <em>all</em> places. Even if they are not on the extern type.</p> <pre><code>/** * @param {AnotherType} */ exp.bar = function (c) { c.other = c.english; } </code></pre> <p>compiles to...</p> <pre><code>function(a){a.b=a.english}; </code></pre> <p>Is there a way to stop this? If not, is there a reason for this behavior? </p> <p>I wanted to use extern types to handle things like JSON objects that originate from the server and do not have renamed properties. But if every time I declare an extern I'm eating away at the compiler's ability to rename and shrink the code, I will find another way. Perhaps I will take the property renaming map generated by the compiler (<code>--property_map_output_file</code>) and use it on the server when generating JSON responses.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USRob N
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
      1. USpimvdb
      1. VTFavorite
    1. COThis is the standard behavior of Closure in order to avoid bugs (you can read the Closure web site to understand why this is necessary). Closure always renames the same property name to the same mangled name. On the flip side, it does not rename all properties (regardless of where) of the same name -- because in essence non-renaming is just renaming to itself. There is a flag (called `ambiguateProperties` or something like that) that you can turn on the avoid this, but it is experimental only.
      singulars
      1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
      1. USStephen Chung
    2. COThe reason for this standard behavior is that you can write a function that just takes an object, and use the `english` property on that object. Closure has no way to know what object you're passing in, and whether that object's `english` property has been renamed or not. Because JavaScript is a non-typed language, you can do this kind of things (by passing in different objects of different classes), so the compiler must rename the same property name to the same string to avoid not being able to decide which version of the name it is mapped to.
      singulars
      1. POCan I tell the Closure compiler to, for specific types only, stop renaming properties?
      1. USStephen Chung
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload