doctor: parse env_files and report lines that resolveEnv rejects #72

Closed
opened 2026-10-19 15:26:43 +02:00 by pti · 0 comments
Owner

Follow-up from PR 64. env_files are now parsed with the dotenv convention and a line without an equals sign, or with an empty name, is an error at tool call time or at MCP server start. wraptool doctor still only checks that each env_files entry exists, is readable and has tight permissions, so a file that fails to parse passes doctor and fails later. Add a doctor check that runs the same parser over each env file and reports file and line number, never the line content, with a remedy pointing at the Env file format table in docs/configuration.qmd.

Follow-up from PR 64. env_files are now parsed with the dotenv convention and a line without an equals sign, or with an empty name, is an error at tool call time or at MCP server start. wraptool doctor still only checks that each env_files entry exists, is readable and has tight permissions, so a file that fails to parse passes doctor and fails later. Add a doctor check that runs the same parser over each env file and reports file and line number, never the line content, with a remedy pointing at the Env file format table in docs/configuration.qmd.
pti closed this issue 2026-10-19 22:53:55 +02:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pti/wraptool#72
No description provided.