Bugzilla – Bug 610
Migrating to mixed-case properties in HopObject
Last modified: 2008-10-20 14:55:20
You need to log in before you can comment on or make changes to this bug.
Is there any plan to get rid of the lower-case property names in a HopObject? I know it's not a general issue because all properties are generally accessible: var h = new HopObject; h.FOO = "bar"; res.debug(h.FOO === h.foo); // true However, when looping over a HopObject one gets only the lowercase property names: var o = new Bar; // assumed there's a mapping for FOO in Bar.properties for (var i in o) { o[i] = h[i]; // o.FOO will *never* be set, onl o.foo which is unmapped } This leads to unwanted results e.g. when using output via Xml.write/read for exporting and importing data between two applications. What about an application-wide switch for enabling/disabling mixed-case property names in HopObjects?
Adding this bug to version 1.6.3 with only a flicker of hope ;)
Oops! Switched the version instead of the target milestone... correcting.
Just committed to svn: HopObject properties are now case sensitive.
This might break existing apps and data, retargeting to 1.7.0