Skip to content

Resolve every --output the same way: existing directory or trailing slash is a directory, anything else a file - #51

Merged
odrobnik merged 4 commits into
mainfrom
agent/issue-37
Oct 8, 2026
Merged

odrobnik merged 4 commits into
mainfrom
agent/issue-37

Conversation

@odrobnik

@odrobnik odrobnik commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Resolves #37.

odrobnik and others added 3 commits October 8, 2026 08:22
LocalMessageFile.destination(for:named:) had the right rule since #36 —
an existing directory or a trailing slash is a directory, anything else
is the filename to write — but it was private to --part. Move it to
OutputPath so the IMAP-backed commands can share it, split out
namesDirectory for callers that must validate before writing, and test
the rule once on the helper instead of per command.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Fetch kept its own existence check plus a pathExtension test, so an
extensionless --output like 'invoice' became a directory holding
<uid>.eml. Drop the precomputed outputDir and resolve each destination
with the shared rule; an explicit filename now also applies to the
text-body export instead of being ignored.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Both keyed on pathExtension alone, so an existing directory named
exports.v1 or archive.pdf was handed to Data.write as a file, and an
extensionless filename silently became a directory. PDF's own variant
also treated report.pdf.bak as a directory. The multi-UID filename
rejection in pdf survives on top of the shared rule, and the help text
now states the rule instead of 'directory or filename'.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T06:33:11.843193Z 530772b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 530772b1c0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Sources/post/OutputPath.swift
A missing ./backup or ./downloads is now a filename, so the examples
must say ./backup/ to get the directory they describe. The fetch
examples also spelled the option --out, which the parser rejects.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@odrobnik
odrobnik merged commit 2ce4b46 into main Oct 8, 2026
2 checks passed
@odrobnik
odrobnik deleted the agent/issue-37 branch October 8, 2026 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--output resolves directory-vs-file four different ways, two of them wrong

1 participant