Rick Waldron
Rick Waldron
> Can you help me understand what is undefined? For example: > > ```js > (function() { "use strict"; function b() { console.log(this) } b.call({c: 1}) })() > // >...
> PH: What I don’t like about this is that X, Y, Z is repeated twice with X, gyroX, etc. It’s messy. We could do sample.accelerometer.x, sample.gyroscope.x, and so on...
> But, those appear to be minor -- for example relativeHumidity above will be humidity. Is that `humidity` property actually reporting a "relative humidity"?
Sorry, that was lazy of me :| (And thank you for the link and for not calling me out for being lazy)
> @fbender That's the idea behind returning a copy via the getter: It does not matter if the Map gets edited. You always get the "fresh" copy from the getter,...
The terminology mistake is that you're not using the right terminology. The thing you described above is an "accessor" property. I'm missing context for this bombardment of snippets, but I...
Sorry about the weird copy/paste shenanigans... I wrote that in an editor and pasted back, whoops!
So make them `null` when there is no data for the property? Objects without a predictable shape are problematic.
> only known properties end up on the object when you iterate over it. I don't know what you mean by "known properties"
This should be an agenda item, as I'm sure implementers will want to discuss