Fix ztd-cli dogfooding guidance and scaffold stability - #620
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughReplace workspace dependency links with explicit semver ranges across several packages; re-export two modules from core; add --skip-install and npm workspace detection to ztd-cli init; and replace placeholder testkit-client templates with fixture-backed clients plus updated tests and READMEs. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant CLI
participant FSys as File System
participant NPM as NPM Workspace
participant Installer as Dependency Installer
User->>CLI: run `ztd init` [--skip-install]
CLI->>FSys: generate scaffold files
FSys-->>CLI: scaffold created
alt skipInstall true
CLI->>User: show install instruction note
else
CLI->>NPM: detect ancestor workspace (resolveNpmWorkspaceGuard)
NPM-->>CLI: workspace info or null
alt nested workspace detected
CLI->>Installer: run `npm install --workspaces=false`
else
CLI->>Installer: run `npm install`
end
Installer-->>CLI: success or failure
alt failure
CLI->>User: "Dependency install failed, but scaffold created" + note
else
CLI->>User: include install step in next-steps
end
end
CLI->>User: display final next-steps summary
sequenceDiagram
participant Test
participant Executor as Testkit Executor
participant Parser as Query Parser
participant Fixtures as Fixture Store
participant Projector as Result Projector
Test->>Executor: createTestkitClient(fixtures)
Executor-->>Test: TestkitClient (query, close)
Test->>Executor: client.query(sql, params)
Executor->>Parser: parse SQL (table, columns, where)
Parser-->>Executor: parsed info
Executor->>Fixtures: find fixture rows for table
Fixtures-->>Executor: fixture rows
Executor->>Executor: resolve $n params and filter rows
Executor->>Projector: project requested columns
Projector-->>Executor: result rows
Executor-->>Test: return rows
Test->>Executor: close()
Executor-->>Test: resolved
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 8
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/ztd-cli/templates/tests/queryspec.example.test.ts (1)
48-54:⚠️ Potential issue | 🟠 MajorKeep the mocked SQL consistent with the declared params.
listActiveUsersSpecdeclaresexample: [], and Line 101 callsexecutor.list(listActiveUsersSpec, []), but Line 87 still returns SQL with$1. That query unit is internally inconsistent and cannot be copied into a real repository without changing either the SQL or the params contract.Based on learnings
The first SQL-backed repository should be mirrored in tests/queryspec.example.test.ts so SQL, QuerySpec, and tests stay aligned.Also applies to: 83-109
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/ztd-cli/templates/tests/queryspec.example.test.ts` around lines 48 - 54, The mocked SQL returned for listActiveUsersSpec is inconsistent with its declared params: listActiveUsersSpec sets example: [] and executor.list(listActiveUsersSpec, []) is called, but the mocked SQL still contains a $1 parameter; update the test fixture so the SQL, QuerySpec, and invocation match by either removing the $1 from the mocked SQL (make it a no-parameter query) or changing listActiveUsersSpec.params.example and the executor.list call to supply a positional parameter; locate listActiveUsersSpec, the mocked SQL string (the SQL returned on line ~87), and the executor.list invocation to make the change so all three (QuerySpec, SQL, and test call) are consistent.
🧹 Nitpick comments (1)
packages/ztd-cli/templates/tests/support/testkit-client.webapi.ts (1)
3-128: Consider sharing this helper with the default template variant.Aside from the
SqlClientimport path, this is the same fixture parser/executor aspackages/ztd-cli/templates/tests/support/testkit-client.ts. Pulling the shared logic into one template helper would keep future fixes and supported SQL shapes from drifting between the default and WebAPI scaffolds.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/ztd-cli/templates/tests/support/testkit-client.webapi.ts` around lines 3 - 128, This file duplicates the fixture parser/executor found in the default template; extract the shared logic — TestkitClient type, tableFixture, parseSelectQuery, normalizeIdentifier, resolveTableRows, resolveWhereValue, projectRows, filterRows and the core createTestkitClient implementation — into a single shared helper module and have both the WebAPI variant and the default template import and adapt that helper (keeping only the WebAPI-specific SqlClient import/adapter in this file). Ensure the WebAPI file delegates to or re-exports the shared createTestkitClient so future fixes to SQL parsing/fixtures are applied in one place.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/adapters/adapter-node-pg/package.json`:
- Around line 35-39: The package.json dependency entries (e.g., "pg",
"rawsql-ts", "@rawsql-ts/testkit-postgres", "@rawsql-ts/testkit-core",
"@rawsql-ts/shared-binder") were manually changed from workspace:^ to fixed
semver—revert those direct edits in package.json back to the workspace:^ entries
and do not commit manual version bumps; then run pnpm install from the repo root
to regenerate the lockfile so changes to the lock are consistent with the
workspace manifests, or if a version bump is required follow the release
workflow tooling instead of editing package.json directly.
In `@packages/testkit-core/package.json`:
- Line 41: The package version for "rawsql-ts" was edited directly in
package.json causing a lockfile mismatch with pnpm-lock.yaml; either revert the
package.json change back to the workspace specifier for "rawsql-ts" or, if the
version bump is intentional, run pnpm install to regenerate pnpm-lock.yaml so
the lockfile and manifest agree, then commit both the updated package.json and
the regenerated pnpm-lock.yaml (referencing the "rawsql-ts" manifest entry and
pnpm-lock.yaml); do not directly edit package.json without updating the
lockfile.
In `@packages/testkit-postgres/package.json`:
- Around line 35-37: You edited dependency versions directly in
packages/testkit-postgres/package.json for "@rawsql-ts/sql-contract",
"@rawsql-ts/testkit-core", and "rawsql-ts", which requires synchronizing the
lockfile; revert manual version bumps (restore workspace:^ entries if they were
changed) or follow the release workflow, then run pnpm install to regenerate
pnpm-lock.yaml and commit the updated lockfile so the lock matches package.json;
do not manually edit package.json versions outside the release/publish process.
In `@packages/ztd-cli/src/commands/init.ts`:
- Around line 251-252: The early return used when the --skip-install flag is set
(and the install-failure fallback) skips the step that adds template-only
packages computed by ensurePackageJsonFormatting(), so package.json can be left
missing required template deps; update the --skip-install branch and the
install-error fallback to still call ensurePackageJsonFormatting() (or the same
logic that computes and injects missingPackages including template-only packages
like `@rawsql-ts/sql-contract`) and persist the updated package.json before
returning, and ensure the fallback note generation includes the exact "install
-D ..." command string so users can run the correct install command manually.
In `@packages/ztd-cli/templates/README.webapi.md`:
- Around line 73-77: Update the README reference that points to
tests/support/testkit-client.webapi.ts to the actual emitted helper filename
tests/support/testkit-client.ts (and adjust any other mentions of
testkit-client.webapi.ts in the README), so readers are directed to the file the
scaffold actually generates; keep the other example filenames
(tests/queryspec.example.test.ts, tests/smoke.test.ts) unchanged.
In `@packages/ztd-cli/templates/tests/queryspec.example.test.ts`:
- Around line 33-39: The list implementation in createCatalogExecutor currently
passes raw row objects from executor(...) directly into spec.output.validate,
causing DTO fields to be undefined; update the logic in createCatalogExecutor ->
list to first apply spec.output.mapping (if present) to each raw row to produce
the transformed DTO, then run spec.output.validate (if present) on that mapped
object before returning; keep using loader.load(spec.sqlFile) and executor(sql,
params) as-is but replace the rows.map callback to perform mapping then
validation in that order.
- Around line 3-31: Replace the local QuerySpec type and rowMapping shim with
the real exports from `@rawsql-ts/sql-contract`: import QuerySpec and RowMapping
(and any helper rowMapping function) and use those instead of the inline
definitions; ensure the imported QuerySpec uses params.shape that accepts
'positional' | 'named', makes output.mapping optional and typed as
RowMapping<R>, and marks notes as optional, and make rowMapping return a
RowMapping instance rather than a plain object; keep CatalogExecutorOptions but
switch any mapping usage to the imported RowMapping type to stay aligned with
the library API.
In `@packages/ztd-cli/templates/tests/support/testkit-client.ts`:
- Around line 47-63: In resolveWhereValue, ensure positional parameter
references actually exist: after computing index = Number(whereValue.slice(1))
and validating it, check that values is an array and that values.length >=
index; if the slot is missing (index-1 out of bounds) throw a clear Error (e.g.,
`Missing positional parameter for ${whereValue}`) instead of returning
undefined; update resolveWhereValue to perform this bounds check before
returning values[index - 1].
---
Outside diff comments:
In `@packages/ztd-cli/templates/tests/queryspec.example.test.ts`:
- Around line 48-54: The mocked SQL returned for listActiveUsersSpec is
inconsistent with its declared params: listActiveUsersSpec sets example: [] and
executor.list(listActiveUsersSpec, []) is called, but the mocked SQL still
contains a $1 parameter; update the test fixture so the SQL, QuerySpec, and
invocation match by either removing the $1 from the mocked SQL (make it a
no-parameter query) or changing listActiveUsersSpec.params.example and the
executor.list call to supply a positional parameter; locate listActiveUsersSpec,
the mocked SQL string (the SQL returned on line ~87), and the executor.list
invocation to make the change so all three (QuerySpec, SQL, and test call) are
consistent.
---
Nitpick comments:
In `@packages/ztd-cli/templates/tests/support/testkit-client.webapi.ts`:
- Around line 3-128: This file duplicates the fixture parser/executor found in
the default template; extract the shared logic — TestkitClient type,
tableFixture, parseSelectQuery, normalizeIdentifier, resolveTableRows,
resolveWhereValue, projectRows, filterRows and the core createTestkitClient
implementation — into a single shared helper module and have both the WebAPI
variant and the default template import and adapt that helper (keeping only the
WebAPI-specific SqlClient import/adapter in this file). Ensure the WebAPI file
delegates to or re-exports the shared createTestkitClient so future fixes to SQL
parsing/fixtures are applied in one place.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0f4911f6-a3a7-490b-b628-fcbd96872ae7
⛔ Files ignored due to path filters (1)
packages/ztd-cli/tests/__snapshots__/init.command.test.ts.snapis excluded by!**/*.snap
📒 Files selected for processing (15)
packages/adapters/adapter-node-pg/package.jsonpackages/core/src/index.tspackages/testkit-core/package.jsonpackages/testkit-postgres/package.jsonpackages/ztd-cli/package.jsonpackages/ztd-cli/src/commands/init.tspackages/ztd-cli/templates/README.mdpackages/ztd-cli/templates/README.webapi.mdpackages/ztd-cli/templates/src/infrastructure/persistence/README.mdpackages/ztd-cli/templates/tests/queryspec.example.test.tspackages/ztd-cli/templates/tests/smoke.test.tspackages/ztd-cli/templates/tests/support/testkit-client.tspackages/ztd-cli/templates/tests/support/testkit-client.webapi.tspackages/ztd-cli/tests/init.command.test.tspackages/ztd-cli/vitest.config.ts
Comment on lines
+35
to
+39
| "@rawsql-ts/testkit-postgres": "^0.15.3", | ||
| "@rawsql-ts/testkit-core": "^0.16.1", | ||
| "@rawsql-ts/shared-binder": "^0.0.1", | ||
| "pg": "^8.13.1", | ||
| "rawsql-ts": "workspace:^" | ||
| "rawsql-ts": "^0.17.0" |
There was a problem hiding this comment.
Same lockfile synchronization concern as other package manifests.
These workspace:^ → semver version changes follow the same pattern across the PR. Ensure pnpm install regenerates the lockfile after all manifest changes are complete.
As per coding guidelines, direct version edits are prohibited outside of release workflows.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/adapters/adapter-node-pg/package.json` around lines 35 - 39, The
package.json dependency entries (e.g., "pg", "rawsql-ts",
"@rawsql-ts/testkit-postgres", "@rawsql-ts/testkit-core",
"@rawsql-ts/shared-binder") were manually changed from workspace:^ to fixed
semver—revert those direct edits in package.json back to the workspace:^ entries
and do not commit manual version bumps; then run pnpm install from the repo root
to regenerate the lockfile so changes to the lock are consistent with the
workspace manifests, or if a version bump is required follow the release
workflow tooling instead of editing package.json directly.
Comment on lines
+35
to
+37
| "@rawsql-ts/sql-contract": "^0.3.1", | ||
| "@rawsql-ts/testkit-core": "^0.16.1", | ||
| "rawsql-ts": "^0.17.0" |
There was a problem hiding this comment.
Direct version edits require lockfile synchronization.
Same pattern as testkit-core/package.json — these workspace:^ → semver changes require the lockfile to be regenerated. Ensure pnpm install is run after these changes to update pnpm-lock.yaml.
As per coding guidelines, editing package versions directly in package.json is prohibited unless this is part of a release/publish workflow.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/testkit-postgres/package.json` around lines 35 - 37, You edited
dependency versions directly in packages/testkit-postgres/package.json for
"@rawsql-ts/sql-contract", "@rawsql-ts/testkit-core", and "rawsql-ts", which
requires synchronizing the lockfile; revert manual version bumps (restore
workspace:^ entries if they were changed) or follow the release workflow, then
run pnpm install to regenerate pnpm-lock.yaml and commit the updated lockfile so
the lock matches package.json; do not manually edit package.json versions
outside the release/publish process.
Comment on lines
+251
to
252
| '@rawsql-ts/ztd-cli': '^0.20.3', | ||
| }; |
There was a problem hiding this comment.
--skip-install currently skips declaring template deps, not just installing them.
ensurePackageJsonFormatting() no longer records template-only packages like @rawsql-ts/sql-contract; this function adds them only after it computes missingPackages. The early return on Lines 1526-1529 skips that step entirely, so a scaffold created with --skip-install can tell the user to run a plain install even though package.json is still missing required imports. The same problem shows up on the install-failure path, where the fallback note loses the exact install -D ... command.
Based on learnings Template changes MUST preserve an executable pnpm test path for initialized projects.
Also applies to: 1526-1575
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ztd-cli/src/commands/init.ts` around lines 251 - 252, The early
return used when the --skip-install flag is set (and the install-failure
fallback) skips the step that adds template-only packages computed by
ensurePackageJsonFormatting(), so package.json can be left missing required
template deps; update the --skip-install branch and the install-error fallback
to still call ensurePackageJsonFormatting() (or the same logic that computes and
injects missingPackages including template-only packages like
`@rawsql-ts/sql-contract`) and persist the updated package.json before returning,
and ensure the fallback note generation includes the exact "install -D ..."
command string so users can run the correct install command manually.
Comment on lines
+73
to
+77
| Good example files to start from: | ||
|
|
||
| * `tests/queryspec.example.test.ts` for the `QuerySpec + CatalogExecutor` path | ||
| * `tests/smoke.test.ts` for the fixture-backed ZTD rewrite path | ||
| * `tests/support/testkit-client.webapi.ts` for the testkit client helper |
There was a problem hiding this comment.
Point readers at the emitted helper filename.
The WebAPI scaffold still writes this helper as tests/support/testkit-client.ts; tests/support/testkit-client.webapi.ts only exists in the template source. The current docs will send scaffold users to a file that is not generated.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ztd-cli/templates/README.webapi.md` around lines 73 - 77, Update the
README reference that points to tests/support/testkit-client.webapi.ts to the
actual emitted helper filename tests/support/testkit-client.ts (and adjust any
other mentions of testkit-client.webapi.ts in the README), so readers are
directed to the file the scaffold actually generates; keep the other example
filenames (tests/queryspec.example.test.ts, tests/smoke.test.ts) unchanged.
Comment on lines
+3
to
+31
| type QuerySpec<TParams extends readonly unknown[], TRow> = { | ||
| id: string; | ||
| sqlFile: string; | ||
| params: { | ||
| shape: 'positional'; | ||
| example: TParams; | ||
| }; | ||
| output: { | ||
| mapping: { | ||
| name: string; | ||
| key: string; | ||
| columnMap: Record<string, string>; | ||
| }; | ||
| validate?: (value: unknown) => TRow; | ||
| example: TRow; | ||
| }; | ||
| notes: string; | ||
| }; | ||
|
|
||
| type CatalogExecutorOptions = { | ||
| loader: { | ||
| load(sqlFile: string): Promise<string>; | ||
| }; | ||
| executor: (sql: string, params: readonly unknown[]) => Promise<Record<string, unknown>[]>; | ||
| }; | ||
|
|
||
| function rowMapping(mapping: { name: string; key: string; columnMap: Record<string, string> }) { | ||
| return mapping; | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
sed -n '35,60p' packages/sql-contract/src/catalog/index.ts
sed -n '426,431p' packages/sql-contract/src/mapper/index.tsRepository: mk3008/rawsql-ts
Length of output: 831
Replace this local QuerySpec and rowMapping shim with imports from @rawsql-ts/sql-contract.
The template defines a local type that diverges from the actual exported API:
mappingshould be optional and typed asRowMapping<R>, not a required plain objectparams.shapeshould accept both'positional' | 'named', not just'positional'notesshould be optional, not requiredrowMapping()should return aRowMappinginstance, not the plain object
Since this file serves as the copyable QuerySpec-first sample, users will create code that misaligns with the actual library. Import the real types/helpers instead.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ztd-cli/templates/tests/queryspec.example.test.ts` around lines 3 -
31, Replace the local QuerySpec type and rowMapping shim with the real exports
from `@rawsql-ts/sql-contract`: import QuerySpec and RowMapping (and any helper
rowMapping function) and use those instead of the inline definitions; ensure the
imported QuerySpec uses params.shape that accepts 'positional' | 'named', makes
output.mapping optional and typed as RowMapping<R>, and marks notes as optional,
and make rowMapping return a RowMapping instance rather than a plain object;
keep CatalogExecutorOptions but switch any mapping usage to the imported
RowMapping type to stay aligned with the library API.
Comment on lines
+33
to
+39
| function createCatalogExecutor({ loader, executor }: CatalogExecutorOptions) { | ||
| return { | ||
| async list<TParams extends readonly unknown[], TRow>(spec: QuerySpec<TParams, TRow>, params: TParams) { | ||
| const sql = await loader.load(spec.sqlFile); | ||
| const rows = await executor(sql, params); | ||
| return rows.map((value) => (spec.output.validate ? spec.output.validate(value) : (value as TRow))); | ||
| } |
There was a problem hiding this comment.
Apply output.mapping before validate().
Line 38 passes the raw { user_id, display_name } row straight into validate(). With the current validator, that yields userId: 'undefined' / displayName: 'undefined', so the sample fails once the scaffold test actually runs.
Suggested fix
function createCatalogExecutor({ loader, executor }: CatalogExecutorOptions) {
return {
async list<TParams extends readonly unknown[], TRow>(spec: QuerySpec<TParams, TRow>, params: TParams) {
const sql = await loader.load(spec.sqlFile);
const rows = await executor(sql, params);
- return rows.map((value) => (spec.output.validate ? spec.output.validate(value) : (value as TRow)));
+ return rows.map((value) => {
+ const mapped = Object.fromEntries(
+ Object.entries(spec.output.mapping.columnMap).map(([field, column]) => [field, value[column]])
+ );
+ return spec.output.validate ? spec.output.validate(mapped) : (mapped as TRow);
+ });
}
};
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ztd-cli/templates/tests/queryspec.example.test.ts` around lines 33 -
39, The list implementation in createCatalogExecutor currently passes raw row
objects from executor(...) directly into spec.output.validate, causing DTO
fields to be undefined; update the logic in createCatalogExecutor -> list to
first apply spec.output.mapping (if present) to each raw row to produce the
transformed DTO, then run spec.output.validate (if present) on that mapped
object before returning; keep using loader.load(spec.sqlFile) and executor(sql,
params) as-is but replace the rows.map callback to perform mapping then
validation in that order.
Comment on lines
+47
to
+63
| function resolveWhereValue(whereValue: string | undefined, values?: readonly unknown[] | Record<string, unknown>): unknown { | ||
| if (!whereValue) { | ||
| return undefined; | ||
| } | ||
|
|
||
| if (whereValue.startsWith('$')) { | ||
| const index = Number(whereValue.slice(1)); | ||
| if (!Number.isFinite(index) || index < 1) { | ||
| throw new Error(`Unsupported parameter reference: ${whereValue}`); | ||
| } | ||
|
|
||
| if (!Array.isArray(values)) { | ||
| throw new Error('Positional parameters are required for fixture-backed queries.'); | ||
| } | ||
|
|
||
| return values[index - 1]; | ||
| } |
There was a problem hiding this comment.
Throw when a referenced bind slot is missing.
Line 62 returns values[index - 1] without checking that the slot exists. A query like ... where id = $2 with only one value silently becomes undefined and filters to zero rows, which hides a broken contract in the generated tests.
Suggested fix
if (whereValue.startsWith('$')) {
const index = Number(whereValue.slice(1));
if (!Number.isFinite(index) || index < 1) {
throw new Error(`Unsupported parameter reference: ${whereValue}`);
}
if (!Array.isArray(values)) {
throw new Error('Positional parameters are required for fixture-backed queries.');
}
+ if (index > values.length) {
+ throw new Error(`Missing value for parameter reference: ${whereValue}`);
+ }
return values[index - 1];
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/ztd-cli/templates/tests/support/testkit-client.ts` around lines 47 -
63, In resolveWhereValue, ensure positional parameter references actually exist:
after computing index = Number(whereValue.slice(1)) and validating it, check
that values is an array and that values.length >= index; if the slot is missing
(index-1 out of bounds) throw a clear Error (e.g., `Missing positional parameter
for ${whereValue}`) instead of returning undefined; update resolveWhereValue to
perform this bounds check before returning values[index - 1].
This was referenced Mar 20, 2026
This was referenced Mar 27, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Verification
Summary by CodeRabbit
New Features
Tests
Documentation
Chores