Skip to content

Support Lottie export jobs - #6

Merged
inlife merged 3 commits into
mainfrom
feat/lottie-jobs
Nov 2, 2026
Merged

inlife merged 3 commits into
mainfrom
feat/lottie-jobs

Conversation

@inlife

@inlife inlife commented Nov 2, 2026

Copy link
Copy Markdown
Member

Summary

  • job submit and batch submit keep settings.lottie. The vendored OpenAPI spec predated the Lottie export, so settings.lottie was dropped without an error when the CLI re-marshalled the payload. openapi/openapi.json is now the current spec from nexrender-api main, and internal/api/api.gen.go is regenerated.
    Other spec changes that came along: frames accepts [start, end, skip] and -1, and PUT /templates/{id}/upload wraps its response in uploadInfo. The CLI doesn't call that endpoint, so nothing else changes.
  • --dry-run says it only validates locally. The flag help and summary on job submit, job join and batch submit now say so. The API can still refuse a payload that passed, for example a lottie job with a codec.
  • Agent skill: calling the API directly. New skills/nexrender/references/api.md covers each profile's base URL, bearer auth, where the CLI keeps the token (env var, keychain with go-keyring's go-keyring-base64: prefix, credentials.json), how to use it in one command without printing it, the main job endpoints, nexrender schema, and Lottie jobs. SKILL.md, operations.md and the README link to it. The skill's existing rules stay: prefer the CLI, never request or print the token, ask before paid renders.

Tests

  • TestJobPayloadKeepsLottieSettings (validate) and TestJobSubmitSendsLottieSettings (the request body job submit sends). Both fail on the old generated code and pass after regeneration.
  • go generate ./internal/api (no diff), gofmt, go test ./..., go vet ./..., go build ./cmd/nexrender, bash -n scripts/install.sh.
  • Staging: job submit --wait with the new binary sent {"type":"lottie","engine":"ae2026","lottie":{"should_encode_images":true}}. The job finished in 8 s, and its zip holds only lottie/data.json, with the image embedded as a data URI and no lottie/images/.
  • The skill's token snippet ran against staging in bash and zsh (GET /jobs), and the token was never printed.

Release

After merge, tag v1.2.0 so nexrender-vanguard can switch its Lottie scenarios from direct API calls to the CLI.

🤖 Generated with Claude Code

inlife and others added 3 commits November 2, 2026 08:10
Vendor the current OpenAPI spec from nexrender-api main. It adds the
"lottie" settings type and the settings.lottie object, so job submit and
batch submit no longer drop Bodymovin's settings when they re-marshal the
payload. The spec also allows [start, end, skip] frame ranges and wraps
the template upload URL response in uploadInfo; the CLI does not call
that endpoint.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
The API runs its own checks on submit, so a payload that passes a dry run
can still be refused (for example a lottie job with a codec).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Add references/api.md: profile base URLs, bearer auth, where the CLI
keeps the token and how to use it without printing it, the main job
endpoints, and Lottie export jobs. Note Lottie export and the local-only
dry run in the README.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@inlife
inlife merged commit fbb6cff into main Nov 2, 2026
2 checks passed
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