Skip to content

Inconsistent CLI validation across tools #23

Description

@calmcacil

Description

Each CLI tool validates its inputs differently, leading to inconsistent user experience.

Examples

  • media-streams checks for missing tokens but does not validate -server values (accepts any string instead of rejecting invalid values)
  • media-calendar does not warn when all configured ArrInstance entries are invalid (empty URL or API key)
  • media-requests does not validate URL format before attempting a connection
  • arr-feed has MaxEvents bounds checking but only at config-build time, not flag-parse time

Proposed Fix

Standardize validation by:

  1. Validating flags at parse time where possible
  2. Rejecting invalid enum-like values (-server) with a clear error message
  3. Adding a shared validation step before executing the main logic

Priority

Low — cosmetic in most cases, but improves DX.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions