Skip to content

fix: nullable brokerage fields and mixed-account balances - #1

Merged
oscargws merged 1 commit into
mainfrom
fix/nullable-holdings-and-mixed-balances
Jul 13, 2026
Merged

oscargws merged 1 commit into
mainfrom
fix/nullable-holdings-and-mixed-balances

Conversation

@oscargws

Copy link
Copy Markdown
Contributor

Found these two while testing the CLI against real accounts.

redbark holdings was crashing on any holding with no name (options, unmatched symbols). The API returns those fields as nullable but the client types didn't, so the render blew up. Fixed the types and the render.

redbark balances with no args failed completely for anyone who also has a brokerage or documents connection. It was sending every account id to /v1/balances, and the API rejects the whole batch if any account isn't a bank account. Now it only asks for banking accounts.

Also made null money values show a dash instead of a blank cell.

Verified against the live API. typecheck, tests and build all pass.

- Mark Holding/Trade fields the API returns as nullable (name, prices,
  fees, dates) nullable in the client types.
- Stop 'redbark holdings' crashing on a null holding name.
- Render null money values as a dash instead of a blank cell.
- 'redbark balances' with no ids now requests only banking accounts, so
  it no longer fails outright for users who also have a brokerage or
  documents connection.
@oscargws
oscargws merged commit 4c17c6a into main Jul 13, 2026
1 check passed
@oscargws
oscargws deleted the fix/nullable-holdings-and-mixed-balances branch July 13, 2026 08:46
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