Skip to content

feat: keep single Template Run output without automatic Dataset - #128

Merged
QThans merged 2 commits into
mainfrom
dev
Sep 24, 2026
Merged

QThans merged 2 commits into
mainfrom
dev

Conversation

@QThans

@QThans QThans commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Make Dataset optional by default for single Template Runs; preserve automatic Dataset for orchestrated Runs.
  • Add owner-scoped, paginated Run output from persisted job results so results remain viewable without a Dataset.
  • Document the behavior and keep explicit New/Existing Dataset choices.

Verification

  • API typecheck and Template Run controller tests (22 passed)
  • DB typecheck/build and job result pagination test (1 passed)

Document the approved single-Run storage behavior, owner-scoped output endpoint, Dashboard flow, compatibility, and verification plan.
Make Dataset output opt-in for single Template Runs, expose owner-scoped paginated job results through the Run resource, and preserve orchestrated automatic Datasets. Add controller and database pagination coverage.
@vercel

vercel Bot commented Sep 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
anycrawl-docs Blocked Blocked Sep 24, 2026 1:00am UTC

@QThans
QThans merged commit 6aa162e into main Sep 24, 2026
5 of 6 checks passed

This branch had an error being deployed

1 failed deployment
Preview — 24fe0aa8 Deployed Sep 24, 2026 by vercel[bot]
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