Skip to content
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

[OI-110] Clang tidy Google Style Guide #155

Merged
merged 8 commits into from
Jul 18, 2023
Merged

Conversation

RReichert
Copy link
Contributor

@RReichert RReichert commented Jun 1, 2023

Changes

We can now specify an option to add further checks for our work in orion-engine for our ASIL compliance. These checks will validate that we are complying with our Google Style Guide.

See: https://github.com/swift-nav/orion-engine/pull/6693 which uses this work to flag non compliance.

- { key: readability-identifier-naming.StructCase, value: CamelCase }
- { key: readability-identifier-naming.TemplateParameterCase, value: CamelCase }
- { key: readability-identifier-naming.VariableCase, value: lower_case }
- { key: readability-identifier-naming.TemplateParameterIgnoredRegexp, value: 'expr-type'}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be added to avoid a bug in clang-tidy that only has been recently been fixed - llvm/llvm-project#46097

@sonarcloud
Copy link

sonarcloud bot commented Jun 1, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@RReichert RReichert changed the title Clang tidy Google Style Guide [OI-110] Clang tidy Google Style Guide Jul 14, 2023
@sonarcloud
Copy link

sonarcloud bot commented Jul 15, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link
Contributor

@silverjam silverjam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we doing this in CMake when this was already implemented in Bazel? We have a mandate (from the VP of engineering and the software VP) to migrate to Bazel, implementing new features in CMake takes us farther away from that goal. CMake should be considered as "maintenance mode" only -- new work in CMake should have a very clear justification why it's not possible in Bazel and DevInfra needs to be made aware so that we can plan to bring Bazel into parity.

ClangTidy.cmake Show resolved Hide resolved
ClangTidy.cmake Show resolved Hide resolved
ClangTidy.cmake Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants