What & why
netwp monitor re-scans on a fixed interval (monitorEvery, 10s). A --interval=<duration> flag would let users slow it down on a big/quiet network or speed it up.
Where
cmd/netwp/live.go (runMonitor, and the headless runMonitorQuiet) and cmd/netwp/main.go (help text).
Scope
- Parse
--interval=30s with time.ParseDuration; fall back to the current default when absent.
- Apply a sane floor (e.g. reject sub-second to avoid hammering the network) with a clear error.
- Pass it into
tui.MonitorConfig.Interval and the headless loop's ticker. Document in both READMEs.
Acceptance
netwp monitor --interval=30s scans every 30s; bad/too-small values fail fast.- Unit test for the duration parse + floor.
- Full verify suite clean.
Good first issue: isolated flag parse; clear boundary.
What & why
netwp monitorre-scans on a fixed interval (monitorEvery, 10s). A--interval=<duration>flag would let users slow it down on a big/quiet network or speed it up.Where
cmd/netwp/live.go(runMonitor, and the headlessrunMonitorQuiet) andcmd/netwp/main.go(help text).Scope
--interval=30swithtime.ParseDuration; fall back to the current default when absent.tui.MonitorConfig.Intervaland the headless loop's ticker. Document in both READMEs.Acceptance
netwp monitor --interval=30sscans every 30s; bad/too-small values fail fast.Good first issue: isolated flag parse; clear boundary.