dangernoodle-io / breadboard / 31134342086

97%

push

github

refactor: collapse four bb_serialize_json variant ladders (B1-1437) (#1244)

bb_serialize_json_render/_ex and bb_serialize_json_stream_compose_render/_ex
had real callers on both rungs -- both collapse into one cfg-struct entry
point (bb_serialize_json_render_cfg_t /
bb_serialize_json_stream_compose_render_cfg_t), mirroring
bb_serialize_walk_cfg_t's own collapse (#1243). bb_serialize_json_render()
no longer matches the shared bb_serialize_render_fn format-dispatch typedef,
so bb_serialize_json_format.c gains a private (non-public) adapter for the
.render registry slot; five host tests that hand-built that same registry
entry now call bb_serialize_json_register_format() instead.

bb_serialize_json_render_ref_ex and bb_serialize_json_stream_render_ex had
zero callers outside their own former thin wrapper -- both merge into their
base fn as a trailing f64_shortest param instead (no cfg struct, per
explicit design ruling), then the _ex is deleted.

Every f64_shortest call site was audited individually to preserve its
existing value (false by default, true only at the two explicit
shortest-round-trip test sites) -- no call site's JSON number formatting
changes.

Flash impact of the touched symbols, by symbol (xtensa nm on both
firmware.elf, examples/smoke esp32): +12 B net (bb_serialize_json_render
+7 B, bb_serialize_json_stream_render +88 B absorbing the merged _ex body,
bb_json_format_render new adapter +34 B, bb_http_serialize_stream +12 B,
bb_http_serialize_stream_compose_ex +16 B, offset by
-32/-113/-130 B from the three deleted _ex bodies). Not a whole-image
comparison (unreliable in this repo per B1-1462).

Claude-Session: https://claude.ai/code/session_0119nuE2NZME9y2aYEVJTPB5

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

8534 of 9074 branches covered (94.05%)

Branch coverage included in aggregate %.

16 of 16 new or added lines in 3 files covered. (100.0%)

14279 of 14434 relevant lines covered (98.93%)

2598.39 hits per line