Skip to content

v1.17.4 - V2 File Naming Convention Standardization (2025-12-15)

What Changed?

This release standardizes v2-specific file naming conventions by applying the consistent v2_ prefix to all remaining v2-only files. The detector class and device response builder are now properly named, improving code clarity and maintainability. No user-facing changes—this is a pure organizational refactoring for codebase hygiene.

What's New

Refactoring: V2 Naming Convention Standardization

What it does:

Renames four v2-specific files to use consistent v2_ prefix for clarity and consistency:

  • detector.h → v2_detector.h
  • detector.cpp → v2_detector.cpp
  • device_response_builder.h → v2_device_response_builder.h
  • device_response_builder.cpp → v2_device_response_builder.cpp

Why it matters:

  • Self-documenting code: File names immediately reveal v2-only code without build knowledge
  • IDE navigation: Developers can instantly identify v2 vs shared/v1 files
  • Consistent organization: All v2 implementation files now follow same naming pattern
  • Reduced confusion: No need to reference build configuration to understand code organization

Files changed:

  • 4 files renamed (2 headers, 2 implementations)
  • 5 files updated with new include statements
  • No functional changes (rename-only refactoring)

Installation

Quick Start

# Get the release
git checkout v1.17.4

# Build
task build

# Upload
task upload

# Check it works
task monitor

What's Different from the Last Version?

✅ Added

  • None (refactoring release)

🔧 Changed

  • Renamed detector.h → v2_detector.h
  • Renamed detector.cpp → v2_detector.cpp
  • Renamed device_response_builder.h → v2_device_response_builder.h
  • Renamed device_response_builder.cpp → v2_device_response_builder.cpp
  • Updated include statements in 5 files accordingly

🐛 Fixed

  • None (naming convention only)

Is It Safe to Upgrade?

Backward Compatible: Yes

  • No changes to v1 or v2 detection buffer API or output format
  • All v1 builds (release, dev, wifi) unaffected (v2 files excluded)
  • All v2 builds (next) work identically (pure rename)
  • Pure refactoring with zero user-facing changes
  • Safe to upgrade for all users

Tests Passed

  • ✅ All v1 builds compile without errors (task build, task dev:build)
  • ✅ All v2 builds compile without errors (task next:build)
  • ✅ All pre-commit hooks passed (trailing whitespace, file endings, merge conflicts)
  • ✅ No linker errors (all includes properly updated)

Release Details

  • Date: 2025-12-15
  • Version: v1.17.4
  • Files Changed: 9 (4 renames + 5 includes updated)
  • Build Type: Refactoring (no new features)

Next Steps

  • Consider renaming src/command/ handlers to src/v2_command/ for complete v2 naming consistency (future improvement, not urgent)
  • Monitor for any additional v1/v2 mixing in shared modules
  • Continue codebase organization improvements