A problem with an explicit list in webrtc-stats is that not all of webrtc-stats is Mandatory to Implement in WebRTC 1.0. So the total list will vary based on which stats above that baseline are implemented. A rule seems more flexible than a list here (for every stat above that baseline, be sure to include everything it [references](https://w3c.github.io/webrtc-stats/#dfn-stats-object-reference)). The invariant sought is for every `xxxId` key encountered, `stats.get(stat.xxxId)` must succeed. That seems like an integrity test we could do from webrtc-pc even without domain knowledge of individual stats. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2456#issuecomment-582000208 using your GitHub accountReceived on Tuesday, 4 February 2020 16:40:48 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:49 UTC