feat: Add CachePoint type definition to ContentBlock #142
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
pgrayy
approved these changes
May 30, 2025
jer96
pushed a commit
to lukehau/sdk-python
that referenced
this pull request
Jun 3, 2025
15 tasks
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.
Description
This PR adds a new CachePoint type definition to the ContentBlock class.
Related Issues
No specific issue referenced
Documentation PR
No associated documentation PR required as the changes are self-documented through docstrings
Type of Change
• New feature
Testing
All tests have been successfully executed to verify that the changes do not break existing functionality:
• hatch fmt --linter - Passed with no issues
• hatch fmt --formatter - Passed with no issues
• hatch test --all - All 453 tests passed with only 12 warnings (unrelated to this change)
• Verified that the changes do not break functionality or introduce warnings in consuming repositories
Checklist
• [x] I have read the CONTRIBUTING document
• [x] I have added tests that prove my fix is effective or my feature works
• [x] I have updated the documentation accordingly
• [x] I have added an appropriate example to the documentation to outline the feature
• [x] My changes generate no new warnings
• [x] Any dependent changes have been merged and published