You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: rename onvif_motion_recording to cross_stream_motion_trigger + drop /api/motion/test (#374)
The onvif_motion_recording module has been reduced to a single function
(process_motion_event) whose only job is to fan a motion event out to
streams linked via motion_trigger_source -- the actual "motion recording"
machinery (per-camera config, buffers, retention) was deleted in
878d3f3 along with the corresponding UI section. The filename no
longer matches what the module does; cross-stream motion trigger
propagation is what remained, so rename accordingly.
- git-mv onvif_motion_recording.{c,h} to cross_stream_motion_trigger.{c,h}
- Update header guard LIGHTNVR_ONVIF_MOTION_RECORDING_H ->
LIGHTNVR_CROSS_STREAM_MOTION_TRIGGER_H
- Refresh the file-level doc comment in both files to describe what the
module actually does now, with a one-line note on the rename for grep
archaeology
- Update the six #include sites: main.c, onvif_detection.c,
detection_integration.c, db_motion_config.h, the test file, and the
deleted api_handlers_motion.c
Also delete the /api/motion/test/<stream> endpoint. It's unreachable
from the current UI (the Trigger Test Motion button was removed along
with the Motion Recording section) and nothing else calls it -- the
whole api_handlers_motion.{c,h} pair existed solely for this one route.
Removed files + the route registration + the include in
libuv_api_handlers.c.
No behavior change for running installations. The cross-stream motion
trigger tests continue to pass (5/5).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments