Naming inconsistency about webrtc-stats HOT 8 CLOSED

Perhaps adding *Info instead of *Stats seems more appropriate as these dictionaries do not contain any metrics or statistics.

• RTCCodecInfo
• RTCIceCandidateAttributeInfo

OTOH, RTCCertificateStats could be RTCCertificateInfo for the same reason. I do not feel strongly about it.

from webrtc-stats.

@vr000m I follow your reasoning, however, anything returned from getStats is stats IMHO, not attributes, info or attribute-info. Dictionaries may grow over time and add more data, so I for one would rather see our types here reflect inheritance (RTCStats).

from webrtc-stats.

My personal leaning would be towards "info" - if one wants to know the inheritance hierarchy, one should walk the prototype chain, not try to parse names.
Names need to be 1) unique and 2) memorable. But I can't bring myself to feel strongly about this.

from webrtc-stats.

@alvestrand dictionaries don't have prototypes. Since there's very little enforcement of this inheritance in JS, I would recommend name consistency here. See also w3c/webrtc-pc#275

from webrtc-stats.

If we want to make this a principle, the document needs to state that it is.
I think we should accept the principle.

from webrtc-stats.

Principle seems to be that *Attribute and *Info should go, and *Stats should be added.

from webrtc-stats.

RTCIceCandidateAttributes -> RTCIceCandidateStats is done in #36

from webrtc-stats.

Closing this issue, since both inconsistencies are now resolved.

from webrtc-stats.