dangernoodle-io / breadboard / 25075291670

100%

push

github

feat(bb_registry): Kconfig opt-out per registry entry; collapse bb_log_routes into bb_log (#124)

Each registry-using component gains a Kconfig flag (default-on): CONFIG_BB_OTA_PULL_AUTOREGISTER, CONFIG_BB_OTA_PUSH_AUTOREGISTER, CONFIG_BB_INFO_AUTOREGISTER. Source-side BB_REGISTRY_REGISTER calls and the matching CMake bb_registry_force_register helpers are both gated; flipping a flag to =n removes the route registration but preserves the component's public C API.

bb_log_routes is collapsed back into bb_log, gated by CONFIG_BB_LOG_ROUTES (default-on). When off, the routes source files aren't compiled and bb_http/bb_json/bb_registry drop out of bb_log's PRIV_REQUIRES — headless logging-only consumers no longer drag the HTTP stack. The bb_log_routes component is deleted entirely; survey confirmed zero downstream consumers.

Verified end-to-end on ELEGOO ESP32:
- Defaults: 5 entries register, all four endpoints respond
- CONFIG_BB_OTA_PULL_AUTOREGISTER=n + CONFIG_BB_OTA_PUSH_AUTOREGISTER=n: 3 entries register, /api/ota/check returns 405, /api/info and /api/logs/status still 200

This is the first Kconfig in breadboard. README gains a Kconfig-flags table; CLAUDE.md's Registry section documents the gate pattern and the required CMake-side conditional (without it, -u <symbol> would dangle).

Out of scope: migrating more components into the registry; changing any defaults from on→off; downstream consumer migration.

272 of 272 branches covered (100.0%)

Branch coverage included in aggregate %.

431 of 431 relevant lines covered (100.0%)

147.89 hits per line