Linter for clang-format #150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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/ |
iandareid
approved these changes
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.