⚙️ Extract shared PandocArgs builder for consistent pandoc command construction

[Copilot]

Each output strategy (HTML, PDF, DOCX) was independently constructing pandoc argument lists — duplicating --from, input path, and -o boilerplate with no shared abstraction.

Changes

• New PandocArgs builder (src/strategies/pandoc_args.rs) — centralises all pandoc arg construction:
  • new(input_format, input_path, output_path) — mandatory base args
  • with_template(path) → --template <path> (HTML, PDF)
  • with_pdf_engine(engine) → --pdf-engine=<engine> (PDF)
  • with_reference_doc(path) → --reference-doc <path> (DOCX)
  • build() -> Vec<String> — emits the final arg list
• Strategies refactored (html.rs, pdf.rs, docx.rs) to use the builder via immutable match-chaining rather than mut reassignment
• PandocArgs re-exported from strategies/mod.rs

Usage

// PDF strategy
let builder = PandocArgs::new(ctx.input_format.as_pandoc_format(), ctx.input_path, ctx.output_path)
    .with_pdf_engine("tectonic");
let args = match template_path {
    Some(ref path) => builder.with_template(path.as_str()),
    None => builder,
}
.build();
let args_refs: Vec<&str> = args.iter().map(String::as_str).collect();
run_command("pandoc", &args_refs)?;

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 15⭐
  Check Your Progress