Skip to content

PDFCLOUD-6233 Add pdfRest client API skill - #43

Closed
datalogics-kam wants to merge 1 commit into
pdfrest:mainfrom
datalogics-kam:pdfcloud-6233-new-pdfrest-api-skill
Closed

PDFCLOUD-6233 Add pdfRest client API skill#43
datalogics-kam wants to merge 1 commit into
pdfrest:mainfrom
datalogics-kam:pdfcloud-6233-new-pdfrest-api-skill

Conversation

@datalogics-kam

Copy link
Copy Markdown
Contributor

PDFCLOUD-6233

Why this change

Adding or evolving SDK API helpers currently requires contributors to reconstruct contract discovery, compatibility rules, Pydantic wire transformations, and live-test expectations from several repository sources. This skill makes that path explicit so API work stays consistent and does not accidentally break existing callers.

What changed (high level)

Added a repository-local pdfrest-client-api skill with UI metadata. It requires PDFCloud-API OpenAPI discovery, guides outcome-oriented helper naming and upload-then-execute resource handling, and makes payload models the boundary between ergonomic Python inputs and pdfRest wire requests. The skill also treats additive parameters as forward-compatible only when existing signatures, defaults, input shapes, and response contracts remain intact.

Behavior changes

No runtime SDK behavior changes. Contributors can now invoke the skill when adding a documented pdfRest endpoint or a compatible parameter to an existing PdfRestClient and AsyncPdfRestClient helper. The skill directs them to stop for user direction when an API change cannot be represented without breaking the public SDK contract.

Validation

Validated the skill structure with the bundled skill validator. The commit also passed the repository pre-commit hooks, including Markdown formatting, YAML checks, and configured Ruff and basedpyright hooks. No package unit, live, or matrix tests were run because this change adds contributor guidance only.

Risks and follow-ups

The skill intentionally depends on a locally available PDFCloud-API checkout and its current OpenAPI specification; contributors without that checkout will be prompted for direction rather than implementing against inference. Future API work can refine the skill with demonstrated edge cases, while preserving its compatibility stop condition.

- Add a skill for forward-compatible typed client API changes.
- Require documented API contracts, model-first serialization, and
  sync/async unit and live coverage.

Assisted-by: Codex
@netlify

netlify Bot commented Aug 22, 2026

Copy link
Copy Markdown

Deploy Preview for pdfrest-python ready!

Name Link
🔨 Latest commit 3fa5b27
🔍 Latest deploy log https://app.netlify.com/projects/pdfrest-python/deploys/6a8a1b5a06cb2e00089058a3
😎 Deploy Preview https://deploy-preview-43--pdfrest-python.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

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.

1 participant