Description
Make --user optional for password set and password clear. When --user is omitted, use imap.user from the configuration file (config.yaml).
Current behavior:
# Required
python -m email_processor password set --user your_email@example.com
python -m email_processor password clear --user your_email@example.com
Desired behavior:
# With config containing imap.user
python -m email_processor password set
python -m email_processor password clear
# Explicit --user still overrides
python -m email_processor password set --user other@example.com
Tasks
Acceptance Criteria
Notes
- Config is already loaded for commands that use it; password commands run in a code path where config can be loaded (or we load it only when
--user is missing to avoid breaking password clear without config).
- Consider same fallback for
password clear for consistency.
Implementation: PR #28
Description
Make
--useroptional forpassword setandpassword clear. When--useris omitted, useimap.userfrom the configuration file (config.yaml).Current behavior:
Desired behavior:
Tasks
--useroptional in CLI args forpassword setandpassword clear(required=False)--useris not provided, load config (--configpath) and useimap.user--usernorimap.useris available, error: e.g.--user is required or set imap.user in config__main__flow: ensure config is loaded before password commands when resolving user--userand config fallbackpassword setexamples assume--useris mandatoryAcceptance Criteria
password setandpassword clearwork without--userwhenimap.useris in config--useroverridesimap.userwhen both are presentNotes
--useris missing to avoid breakingpassword clearwithout config).password clearfor consistency.Implementation: PR #28