Repository navigation
feat(ledger): a journal entry names the entity it is for - #250
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
create_journal_entrygains anentity_idargument, so a caller can record a manual journal entry for a subsidiary. Without it the server files the entry on the group parent and refuses the subsidiary's accounts.Changes
robosystems_client/clients/ledger_client.py:create_journal_entry(..., entity_id=None)setsentity_idon theCreateEventBlockRequestwhen given. Omitted, the request is unchanged.Compatibility
Additive facade argument: a client minor. No server change needed:
create-event-blockalready honoursentity_id.Testing
Two new tests (the entity is sent;
UNSETwhen omitted).just test-allpasses.🤖 Generated with Claude Code
https://claude.ai/code/session_014Wxgk4yttBxgdE2uBHT71R