fix(accounts): load ChatAnywhere usage in desktop batch - #128
Merged
Conversation
CatStack-pixe
commented
Sep 13, 2026
CatStack-pixe
left a comment
CatStack-pixe
left a comment
Owner
Author
There was a problem hiding this comment.
Code audit completed for the scoped change. The platform predicate matches the existing batch-usage support path, and the regression test verifies the desktop usage-cell callback and batched request arguments. No blocking findings. Validation: 44 focused frontend tests passed, vue-tsc typecheck passed, and git diff check passed.
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
1 participant
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.
Fix the desktop account usage path for ChatAnywhere API keys. The account table already renders a dedicated usage cell, but the parent batch loader omitted this platform and left batchedUsage empty, so the UI showed a dash. Add ChatAnywhere to the batch-supported platform list and cover the request path with a regression test.
Tests: targeted Vitest, ESLint, vue-tsc, git diff --check.