feat: add max_cache_age parameter to SDK #143
Open
+14
−0
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.
feat: add max_cache_age parameter to SDK
Summary
Adds the
max_cache_ageparameter to the Python SDK, allowing users to control cache freshness for content retrieval. This parameter specifies the maximum age (in seconds) of cached content before triggering a live crawl.Changes:
max_cache_agetoCONTENTS_OPTIONS_TYPESfor validationmax_cache_age: Optional[int] = Noneparameter to allget_contentsoverloads (4 signatures)max_cache_age: Optional[int] = Noneparameter to allfind_similar_and_contentsoverloads (5 signatures)max_cache_agetonest_fieldscalls so it gets nested under "contents" in API requests