Skip to content

Make FlowDTO.status and PlacementSummaryDTO.is_active optional - #28

Merged
mlnchk merged 1 commit into
mainfrom
fix/optional-dto-fields
Sep 11, 2026
Merged

mlnchk merged 1 commit into
mainfrom
fix/optional-dto-fields

Conversation

@mlnchk

@mlnchk mlnchk commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Type-only change to match a Developer API hotfix. No runtime behavior change — the CLI renders whatever the API returns via printResponse, which skips absent fields.

What

In src/lib/api-schemas.ts:

  • FlowDTO.status → optional. flows update no longer returns it; get/list/create/publish still do.
  • PlacementSummaryDTO.is_active → optional. The paywall placements endpoint omits it; placements list/get still return it.

The parallel FlowConfigDTO.status and PlacementDetailDTO.is_active stay required, since those responses still carry the fields.

Verify

pnpm build && pnpm test && pnpm lint && pnpm run check:agent-docs — all green (203 tests passing).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mlnchk
mlnchk force-pushed the fix/optional-dto-fields branch from 3df1940 to 1571b34 Compare September 10, 2026 11:25
@mlnchk
mlnchk merged commit 224b60b into main Sep 11, 2026
4 checks passed
@mlnchk
mlnchk deleted the fix/optional-dto-fields branch September 11, 2026 08:41
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