Skip to content

chore: regenerate SDK (due dates, aged receivables and payables, discharge allocations) - #267

Merged
jfrench9 merged 1 commit into
mainfrom
feature/ar-ap-regen
Oct 20, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
feature/ar-ap-regen

Conversation

@jfrench9

Copy link
Copy Markdown
Member

Summary

Regenerates the SDK and the checked-in GraphQL schema snapshot against the robosystems branch that carries AR/AP aging, so the client covers it end to end:

  • due dates on invoices and bills (robosystems #1884);
  • the aged receivables and payables reads (#1886);
  • discharge allocations and settlement candidates (#1887).

None of this is in a robosystems release yet: v1.19.2 predates all three. #1884 and #1886 are merged; #1887 is open. The new request fields are inert against a server that predates them, and the new GraphQL fields only resolve once that release deploys.

Changes

Regenerated, no hand-written code:

  • models/
    • CreateEventBlockRequest gains due_date and terms_days.
    • EventBlockEnvelope gains due_date.
    • UpdateEventBlockRequest gains due_date and discharge_allocations.
    • New DischargeAllocation (obligation_event_id, amount).
  • api/: the create_event_block / update_event_block docstrings follow the operation descriptions.
  • graphql/schema.graphql:
    • new fields agedReceivables, agedPayables, openItemsForAgent, dischargeCandidates;
    • their types (AgedBalances, AgingBuckets, AgedAgentRow, ControlTieOut, ControlAccount, OpenItem, IntercompanyPair, DischargeCandidates);
    • dueDate on EventBlock;
    • the corrected openReceivables description.
  • No operations/*.graphql document or LedgerClient method selects the new fields yet, so just generate-graphql produces no change. Facade methods come with the app work, in the TypeScript and Python clients together.

Compatibility

ADDITIVE.

  • Every new model field is optional (| None | Unset = UNSET), including due_date on the response envelope, so parsing a response from a server without it is unchanged.
  • No export, signature or existing field changed.

Testing

  • The regen was run by Joey against the local stack on the server branch.
  • just generate-graphql: no change.
  • just test-all: 699 passed, 17 skipped; ruff check and format clean; basedpyright 0 errors.

🤖 Generated with Claude Code

https://claude.ai/code/session_013UXnatpnbiixt1ZVHfdZAP

@jfrench9
jfrench9 merged commit 9e76617 into main Oct 20, 2026
6 checks passed
@jfrench9
jfrench9 deleted the feature/ar-ap-regen branch October 20, 2026 17:29
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