wipIntroducing new endpoint to query for spending state #332
+58
−5
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
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
DKelle
changed the title
DKelle
commented
Nov 15, 2025
| * @param organizationId The organization ID to check spending status for | ||
| * @returns The current spending state including spent amount, daily limit, and window start timestamp | ||
| */ | ||
| async getSpendingStatus(organizationId?: string): Promise<SpendingState> { |
Collaborator
Author
There was a problem hiding this comment.
Need to think more about this method signature. The caller should be agnostic to the org ID. We need some other way to get it from the auth session or similar
Contributor
There was a problem hiding this comment.
I don't think we need expose the option to fetch from other organizations. The SDK is initiated explicitly for one.
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 & Motivation
How I Tested These Changes
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
yarn changeset. This will generate a file where you should write a human friendly summary about the changes. Please respect the versioning system - if any interface has been broken, we need to increase the major version.Did you update the README files?
If the interfaces of affected packages have changed, please ensure their README files are updated to reflect the new APIs and usage patterns.