Skip to content

PDFCLOUD-5464 Add final batch of tools#10

Closed
datalogics-cgreen wants to merge 61 commits intopdfrest:mainfrom
datalogics-cgreen:pdfcloud-5464-everything-else
Closed

PDFCLOUD-5464 Add final batch of tools#10
datalogics-cgreen wants to merge 61 commits intopdfrest:mainfrom
datalogics-cgreen:pdfcloud-5464-everything-else

Conversation

@datalogics-cgreen
Copy link
Copy Markdown
Contributor

No description provided.

Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
Assisted-by: Codex
datalogics-cgreen and others added 26 commits January 7, 2026 09:26
Assisted-by: Codex
- Now evaluates:
  - File names
  - MIME types
  - File sizes
  - Warnings in response
  - Input ID

Assisted-by: Codex
Omit mention of `output_type` as it is not relevant to the caller.

Co-authored-by: Kevin A. Mitchell <kam@datalogics.com>
- Introduced `_bool_to_on_off` function to convert boolean values to "on"/"off".
- Applied the new `BeforeValidator` to `preserve_line_breaks`, `word_style`,
  and `word_coordinates` fields to handle boolean inputs properly.
- Ensured consistency in serialization and validation of relevant model fields.

Assisted-by: Codex
OCR PDF does not extract text, but it makes subsequent text extraction possible.
Assisted-by: Codex
- Add `blank_pdf()` sync and async methods
- Ensure compatibility with Blank PDF response:
  - Allow PdfRestRawFileResponse.input_id to default empty so missing inputId doesn’t fail validation
  - When normalizing file responses, fall back to raw ids (outputId) when inputId is absent for blank-pdf
  - Document blank-pdf handling to keep response construction working without server-provided input ids
@datalogics-cgreen datalogics-cgreen force-pushed the pdfcloud-5464-everything-else branch from b01cb78 to 18562ca Compare January 12, 2026 23:46
@datalogics-kam
Copy link
Copy Markdown
Contributor

Can I propose that we make a PR per tool (or related tools, like when you have redact preview and apply)? That'll make it easier to review in chunks. What do you think?

Also, it means the title/desc will be specific about what the tool is doing.

@datalogics-cgreen
Copy link
Copy Markdown
Contributor Author

Can I propose that we make a PR per tool (or related tools, like when you have redact preview and apply)? That'll make it easier to review in chunks. What do you think?

Also, it means the title/desc will be specific about what the tool is doing.

@datalogics-kam Can do.

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.

2 participants