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

refactor(hesai_hw_interface): case style fixes #238

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mojomex
Copy link
Collaborator

@mojomex mojomex commented Nov 26, 2024

PR Type

  • Improvement

Related Links

  • chore: fix case styles #205 - Hesai HW interface was left out due to other in-flight PRs that would have been a pain to merge at the time

Description

Fix the case style of all symbols in the Hesai hardware interface. This marks the completion of the work started in #205.

Pre-Review Checklist for the PR Author

PR Author should check the checkboxes below when creating the PR.

  • Assign PR to reviewer

Checklist for the PR Reviewer

Reviewers should check the checkboxes below before approval.

  • Commits are properly organized and messages are according to the guideline
  • (Optional) Unit tests have been written for new behavior
  • PR title describes the changes

Post-Review Checklist for the PR Author

PR Author should check the checkboxes below before merging.

  • All open points are addressed and tracked via issues or tickets

CI Checks

  • Build and test for PR: Required to pass before the merge.

Copy link

codecov bot commented Nov 26, 2024

Codecov Report

Attention: Patch coverage is 0% with 206 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (3d42cd0) to head (cc8d563).

Files with missing lines Patch % Lines
.../nebula_hesai_hw_interfaces/hesai_hw_interface.cpp 0.00% 186 Missing ⚠️
nebula_ros/src/hesai/hw_interface_wrapper.cpp 0.00% 8 Missing ⚠️
nebula_ros/src/hesai/hw_monitor_wrapper.cpp 0.00% 7 Missing ⚠️
nebula_ros/src/hesai/hesai_ros_wrapper.cpp 0.00% 5 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (3d42cd0) and HEAD (cc8d563). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (3d42cd0) HEAD (cc8d563)
total 1 0
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #238       +/-   ##
==========================================
- Coverage   26.11%   0.00%   -26.12%     
==========================================
  Files         101      88       -13     
  Lines        9212    7941     -1271     
  Branches     2211     938     -1273     
==========================================
- Hits         2406       0     -2406     
- Misses       6417    7941     +1524     
+ Partials      389       0      -389     
Flag Coverage Δ
differential 0.00% <0.00%> (?)
total ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

const uint16_t PANDAR128_E4X_PACKET_SIZE = 861;
const uint16_t PANDAR128_E4X_EXTENDED_PACKET_SIZE = 1117;
const uint16_t MTU_SIZE = 1500;
const int g_pandar_tcp_command_port = 9347;
Copy link
Collaborator

Choose a reason for hiding this comment

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

In some of my code I am using lots of these as well and was wondering which guidelines did you follow for the g_ prefix. Additionally, would constexpr be better here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This one is (regrettably) part of Autoware's .clang-tidy configuration, which we based ours on:
https://github.com/autowarefoundation/autoware/blob/0e44b14187196ab0fd75a69bf0eee27b086d3b47/.clang-tidy#L447-L448

Also not a fan but I think it's best to keep the projects mostly in sync.

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.

2 participants