commit | 4b96bfde967983e1ca9781c7b11496a76f081f5f | [log] [tgz] |
---|---|---|
author | Boris Tsirkin <btsirkin@meta.com> | Mon Jan 06 16:20:11 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 07 10:05:31 2025 |
tree | 89c5a2f5e1e97daf0dc47db1fbbed77dbf9d4b46 | |
parent | 2b04fb77a1e5c69ff9d81f4a56ff90984c3c1c1e [diff] |
Make .clang-format ObjC respect Chromium column limit length Currently, WebRTC .clang-format file is configured to support column length of up to 100: https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/.clang-format;l=12;drc=73012534918d8c65ae748fff8ca18ad5c857b82e While Google guidelines mention supporting up to 100 (https://google.github.io/styleguide/objcguide.html#line-length), Chromium guidelines mention up to 80, like in C++ (https://chromium.googlesource.com/chromium/src/+/lkgr/styleguide/objective-c/objective-c.md#line-length) WebRTC guidelines mention that in case of conflicts, the Chromium guidelines should be followed (https://webrtc.googlesource.com/src/+/HEAD/g3doc/style-guide.md) Hence, I'm suggesting changing the ObjC ColumnLimit parameter from 100 to 80. Bug: webrtc:387828388 Change-Id: If9186bebec92cb0c01015084c3e47ad210dccc33 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/373620 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#43663}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.