Skip to content

chore: regenerate update-journal-entry docs for in-step flow re-tags #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jfrench9 merged 1 commit into from
Oct 15, 2026
Merged

chore: regenerate update-journal-entry docs for in-step flow re-tags #255

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions robosystems_client/api/robo_ledger_ledger_events/update_journal_entry.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,8 +117,8 @@ def sync_detailed(
items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`)
account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted
entry too, closed month included, since a flow moves no balance; the lines on the other side of the
entry follow when that side carries one flow. Posted entries accept nothing else and are corrected
via `create-event-block(event_type='journal_entry_reversed')`.
entry that were in step with it follow. Posted entries accept nothing else and are corrected via
`create-event-block(event_type='journal_entry_reversed')`.

**Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
Expand Down Expand Up @@ -172,8 +172,8 @@ def sync(
items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`)
account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted
entry too, closed month included, since a flow moves no balance; the lines on the other side of the
entry follow when that side carries one flow. Posted entries accept nothing else and are corrected
via `create-event-block(event_type='journal_entry_reversed')`.
entry that were in step with it follow. Posted entries accept nothing else and are corrected via
`create-event-block(event_type='journal_entry_reversed')`.

**Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
Expand Down Expand Up @@ -222,8 +222,8 @@ async def asyncio_detailed(
items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`)
account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted
entry too, closed month included, since a flow moves no balance; the lines on the other side of the
entry follow when that side carries one flow. Posted entries accept nothing else and are corrected
via `create-event-block(event_type='journal_entry_reversed')`.
entry that were in step with it follow. Posted entries accept nothing else and are corrected via
`create-event-block(event_type='journal_entry_reversed')`.

**Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
Expand Down Expand Up @@ -275,8 +275,8 @@ async def asyncio(
items are replaced atomically, the new set must balance, and a line on a retired (`is_active=false`)
account is refused. `line_flows` sets the cash flow row of the named lines in place, on a posted
entry too, closed month included, since a flow moves no balance; the lines on the other side of the
entry follow when that side carries one flow. Posted entries accept nothing else and are corrected
via `create-event-block(event_type='journal_entry_reversed')`.
entry that were in step with it follow. Posted entries accept nothing else and are corrected via
`create-event-block(event_type='journal_entry_reversed')`.

**Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
Expand Down
8 changes: 5 additions & 3 deletions robosystems_client/models/update_journal_entry_request.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,11 @@ class UpdateJournalEntryRequest:
patch). The new set must still balance (total_debit == total_credit). Omit to leave existing lines untouched.
line_flows (list[JournalEntryLineFlow] | None | Unset): Re-tag lines in place: each named line takes its
`flow_qname` (null clears it), and when every line on that side of the entry then carries one flow, the lines on
the other side not named here take it too, so the cash line and the account line agree. Allowed on a posted
entry, closed month included, and the only change one accepts; recorded on the entry as `flow_retags`. Not
combinable with `line_items`, which replaces the lines (set `flow_qname` on them).
the other side not named here follow when they were in step with it — untagged, or carrying the flow the named
lines carried before — so the cash line and the account line agree; a line tagged differently on purpose keeps
its tag. Allowed on a posted entry, closed month included, and the only change one accepts; recorded on the
entry as `flow_retags`, with what each changed line carried before. Not combinable with `line_items`, which
replaces the lines (set `flow_qname` on them).
"""

entry_id: str
Expand Down
Loading