mono - refactor: remove ttlSupport property from all storage adapters#1842
mono - refactor: remove ttlSupport property from all storage adapters#1842
Conversation
The ttlSupport property is no longer needed as Keyv now automatically handles TTL support detection. Removed from sqlite, mongo, postgres, dynamo, valkey, etcd, mysql, and memcache adapters. Updated etcd to use direct opts.ttl check instead of the removed property, and updated related tests to verify behavior without ttlSupport. https://claude.ai/code/session_01XambjE8LDvEZ7zSXKnhpuR
Summary of ChangesHello @jaredwray, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request streamlines the Keyv storage adapter codebase by eliminating the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly removes the ttlSupport property from all specified storage adapters, aligning with the core Keyv change that makes this property obsolete. The refactoring is consistent across all adapters. The logic in the etcd adapter and its tests have been appropriately updated to reflect the removal of ttlSupport. I have one suggestion regarding a test case in the MySQL adapter that has been weakened as a result of this change.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1842 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 32 32
Lines 2446 2432 -14
Branches 451 447 -4
=========================================
- Hits 2446 2432 -14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The test only checked that the object was defined after removing ttlSupport, providing no meaningful coverage for the intervalExpiration behavior. https://claude.ai/code/session_01XambjE8LDvEZ7zSXKnhpuR
The ttlSupport property is no longer needed as Keyv now automatically
handles TTL support detection. Removed from sqlite, mongo, postgres,
dynamo, valkey, etcd, mysql, and memcache adapters. Updated etcd to
use direct opts.ttl check instead of the removed property, and updated
related tests to verify behavior without ttlSupport.
https://claude.ai/code/session_01XambjE8LDvEZ7zSXKnhpuR