f4abcc0bbb
This means that these stats will be filtered out by JavaScript unless the conditions for exposing hardware capabilities are met. These conditions are described in the webrtc-stats spec at https://w3c.github.io/webrtc-stats/#limiting-exposure-of-hardware-capabilities. R=hbos@webrtc.org Bug: chromium:1369050,chromium:1369049 Change-Id: I05bdb72ef6789417488c7e786e8713ce99a91f8a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/279960 Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Evan Shrubsole <eshr@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38594}
How to write code in the api/ directory
Mostly, just follow the regular style guide, but:
- Note that
api/code is not exempt from the “.hand.ccfiles come in pairs” rule, so if you declare something inapi/path/to/foo.h, it should be defined inapi/path/to/foo.cc. - Headers in
api/should, if possible, not#includeheaders outsideapi/. It’s not always possible to avoid this, but be aware that it adds to a small mountain of technical debt that we’re trying to shrink. .ccfiles inapi/, on the other hand, are free to#includeheaders outsideapi/.
That is, the preferred way for api/ code to access non-api/ code is to call
it from a .cc file, so that users of our API headers won’t transitively
#include non-public headers.
For headers in api/ that need to refer to non-public types, forward
declarations are often a lesser evil than including non-public header files. The
usual rules still apply, though.
.cc files in api/ should preferably be kept reasonably small. If a
substantial implementation is needed, consider putting it with our non-public
code, and just call it from the api/ .cc file.