Page MenuHomePhabricator

Introduce and run clang-format updated to newer version
ClosedPublic

Authored by marcin on May 17 2022, 6:10 AM.
Tags
None
Referenced Files
F3436429: D4064.diff
Mon, Dec 9, 5:03 AM
F3436268: D4064.diff
Mon, Dec 9, 4:14 AM
F3436100: D4064.diff
Mon, Dec 9, 3:24 AM
F3435953: D4064.diff
Mon, Dec 9, 2:35 AM
F3435809: D4064.diff
Mon, Dec 9, 1:47 AM
F3435674: D4064.diff
Mon, Dec 9, 12:57 AM
F3435521: D4064.diff
Mon, Dec 9, 12:08 AM
F3435375: D4064.diff
Sun, Dec 8, 11:19 PM

Details

Summary

Update clang-format to v1.8.0 since 1.7.0 does not work on Intel

Test Plan

Check that yarn clang-format-all works on Intel mac

Diff Detail

Repository
rCOMM Comm
Branch
marcin/eng-1155
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

tomek added 1 blocking reviewer(s): ashoat.
tomek added inline comments.
native/ios/Comm/CommSecureStore.mm
31

It's really interesting why the code that isn't properly formatted happened to be landed

yarn.lock
15692

(This is because of https://github.com/CommE2E/comm/commit/33f1104ae4759296ae9f7cc1601ee0602086e06a. I ran yarn cleaninstall before landing to make sure no changes showed up in working copy... but then when I ran yarn cleaninstall this morning the change removing shelljs@^0.8.5 showed up in my working copy. Pretty likely it was an omission on my end, but I'm typically pretty paranoid about running yarn cleaninstall once or twice to make sure yarn.lock has everything in it.)

This revision is now accepted and ready to land.May 17 2022, 12:47 PM