The PR does not include the formatting input file .clang-format, but it could. At the moment, its expected to live in the repository itself. See https://github.com/mdolab/tacs_orig/pull/77 that contains a custom file. We could include it here as the default set, and do some check and use the repo one if it exists (similar to flake8).
Expected time until merged
No urgency.
Type of change
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[ ] Maintenance update
[ ] Other (please describe)
Testing
Checklist
[ ] I have run flake8 and black to make sure the code adheres to PEP-8 and is consistently formatted
[ ] I have run unit and regression tests which pass locally with my changes
[ ] I have added new tests that prove my fix is effective or that my feature works
Purpose
Add an option that can be used if clang-format is supposed to be run. This could be included to https://github.com/mdolab/tacs_orig/pull/77 as part of that PR.
The PR does not include the formatting input file
.clang-format, but it could. At the moment, its expected to live in the repository itself. See https://github.com/mdolab/tacs_orig/pull/77 that contains a custom file. We could include it here as the default set, and do some check and use the repo one if it exists (similar to flake8).Expected time until merged
No urgency.
Type of change
Testing
Checklist
flake8andblackto make sure the code adheres to PEP-8 and is consistently formatted