What
To my understanding (may be this needs clarification @NicolasFussberger ), we are using this naming schema for member variable
my_member_variable_
However in alive_monitor code (and most probably also somewhere else) for historical reasons there are also other styles used, like m_recovery_client or _my_member_variable.
So the task here is to unify this with a clang-tidy rule. Also make sure that introduction of wrongly named variables is not possible. Normally this should work out of the box, as clang-tidy is executed as pre-commit hook.
Acceptance Criteria (DoD)
- Unified naming schema
- Introduction of invalid named member variables is impossible (as long as precommit hook is not skipped)
How
No response
What
To my understanding (may be this needs clarification @NicolasFussberger ), we are using this naming schema for member variable
my_member_variable_However in alive_monitor code (and most probably also somewhere else) for historical reasons there are also other styles used, like
m_recovery_clientor_my_member_variable.So the task here is to unify this with a clang-tidy rule. Also make sure that introduction of wrongly named variables is not possible. Normally this should work out of the box, as clang-tidy is executed as pre-commit hook.
Acceptance Criteria (DoD)
How
No response