postgres - feat: moving to properties#1858
Conversation
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 significantly refactors 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
The pull request refactors the KeyvPostgres class to use private properties with getters and setters instead of a single opts object. This improves encapsulation and provides more granular control over configuration options. The changes also include updating the constructor logic and SQL queries to use these new properties. New tests have been added to verify the correct behavior of the properties.
storage/postgres/src/index.ts
Outdated
| // biome-ignore lint/suspicious/noExplicitAny: type format | ||
| public get ssl(): any { |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 35d3058edc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
storage/postgres/src/index.ts
Outdated
| namespace?: string, | ||
| ): AsyncGenerator<[string, string], void, unknown> { | ||
| const limit = Number.parseInt(String(this.opts.iterationLimit!), 10) || 10; | ||
| const limit = this._iterationLimit; |
There was a problem hiding this comment.
Reintroduce iterator limit fallback
iterator() now uses this._iterationLimit directly, but the previous implementation normalized with parseInt(...) || 10. If callers pass iterationLimit: 0, NaN, or another invalid runtime value (common with untyped JS/env-driven config), the query will run with a zero/invalid LIMIT, so iteration can silently return no rows or fail instead of using the default batch size. This is a behavior regression that can cause missed keys during iteration.
Useful? React with 👍 / 👎.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1858 +/- ##
=======================================
Coverage 99.95% 99.95%
=======================================
Files 32 32
Lines 2439 2493 +54
Branches 439 446 +7
=======================================
+ Hits 2438 2492 +54
Misses 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
postgres - feat: moving to properties