Add support for cached tokens in cost calculation #222
Conversation
This file contains 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
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This reverts commit ff4aee0.
Add docs link
add names of the corresponding methods to various structs (same as using methodswith...)
Authored-by: Pablo Valdunciel <[email protected]>
svilupp
force-pushed
the
feature/cached-tokens-cost-calculation
branch
from
0c34f50 to
2117e1c
Compare
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.
Add support for cached tokens in cost calculation
This pull request implements support for cached tokens in the cost calculation function. It addresses the issue described in #215.
Changes
Testing
The changes have been tested with various scenarios, including:
Please review and let me know if any further changes or tests are needed.
If you have any feedback, you can leave comments in the PR and I'll address them in the app!