5a92577a94
Typically, remote candidates come from signalling and are deserialized into C++ objects. The network_type field of these candidates is always ADAPTER_TYPE_UNKNOWN. However, in tests it is common to pass SDP and remote candidates as C++ objects. In this case, the network_type property of remote candidates is preserved, so DCHECK might be triggered when GetStats is called. Clearing fields that are not suitable as remote candidates fixes this issue. Bug: None Change-Id: Ida01b0224bce5cf3e87bcad1ddaca35c9f4fffe7 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/279680 Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Auto-Submit: Daniel.L (Byoungchan) Lee <daniel.l@hpcnt.com> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38436}
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.