bsutherland333
commented
9 months ago Before approving, review the formatting for the codebase and consider if there is anything you'd change. It would be great if we could decide on one coding standard for the whole ROSflight ecosystem. Notice that clang-format does not check naming conventions. You can see the current ROSflight naming conventions here (open to change): https://docs.rosflight.org/v2.0-beta.1/contributing/style-guide/
To help maintain a more consistent coding style, I've added an automatic clang-format compliance check, similar to what is found in the rosflight_firmware repo. I've also tweaked the clang-format file slightly, to improve the readability of class initialization lists.