-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: apply cpp linting and formatting to ncrypto #55362
base: main
Are you sure you want to change the base?
Conversation
Review requested:
|
CC @nodejs/crypto |
Oh nice. Thank you. I've been meaning to get to this. Very helpful |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #55362 +/- ##
==========================================
- Coverage 88.40% 87.91% -0.50%
==========================================
Files 654 654
Lines 187637 187655 +18
Branches 36098 35803 -295
==========================================
- Hits 165887 164977 -910
- Misses 14994 15877 +883
- Partials 6756 6801 +45 |
btw, the intention is to move ncrypto out to a separate repo once all of the work is done to separate it out. It'll be a while tho. At that time that separate project will have its own build and linting stuff |
This comment was marked as outdated.
This comment was marked as outdated.
Hey, can someone restart the failed builds so this fix can land? Thanks! |
c48c984
to
bb8a7d2
Compare
@jasnell would you mind re-approving + CI-ing now that a new commit has been added? |
CC @jasnell (who appears to have contributed most of this work)
If these files are maintained in this repository, should they not follow the same linting / formatting rules? This PR has
clang-format
andcpplint
apply to these files.