fix: ClickHouse form follow-ups from #8028 review#8092
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughClickHouse configuration handling now trims relevant fields, validates ports after trimming, normalises payload values, and ignores equivalent formatting when checking dirtiness. The form displays accessible invalid-port feedback, records connection-test failures as errored without the previous failure toast, and specifies new-password autocomplete for the password field. Tests cover whitespace handling for ports, hosts, payload fields, and passwords. Estimated code review effort: 2 (Simple) | ~10 minutes 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 |
|
@themis-blindfold review |
Docker builds report
|
⚖️ Themis judgement: ✅ Ship itTidy follow-up to #8028 addressing four review comments: whitespace trimming on pasted values (password intentionally left intact), inline port-range validation, removal of redundant danger toasts on test failure, and
CI: unit tests, lint, and typecheck passed. E2E runs were still in progress; build and static-analysis checks all succeeded. 📝 Walkthrough
🧪 How to verify
Automate: the existing unit tests cover trimming, port validation, and payload shape; no additional automated checks needed beyond E2E coverage of the warehouse tab. Product take: Minor UX polish — prevents accidental whitespace in connection details from causing confusing failures, and stops duplicate error feedback on a failed test. Nice quality-of-life improvement but not a capability change. 🧭 Assumptions & unverified claimsNo unverified assumptions or claims. A clean diff that trims the fat (and the whitespace) — exactly what follow-ups should look like. · reviewed at 56d8b6a |
✅ private-cloud · depot-ubuntu-latest-16 — run #18705 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
🗂️ Previous results✅ private-cloud · depot-ubuntu-latest-arm-16 — run #18705 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
✅ oss · depot-ubuntu-latest-16 — run #18705 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)Details
✅ oss · depot-ubuntu-latest-arm-16 — run #18705 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
✅ private-cloud · depot-ubuntu-latest-arm-16 — run #18704 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
✅ private-cloud · depot-ubuntu-latest-16 — run #18704 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
✅ oss · depot-ubuntu-latest-16 — run #18704 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)Details
✅ oss · depot-ubuntu-latest-arm-16 — run #18704 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
✅ private-cloud · depot-ubuntu-latest-16 — run #18693 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
✅ private-cloud · depot-ubuntu-latest-arm-16 — run #18693 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
✅ oss · depot-ubuntu-latest-arm-16 — run #18693 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
✅ oss · depot-ubuntu-latest-16 — run #18693 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)Details
|
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 06fcfd4b-3c7e-450e-b31b-827090bacf5d
📒 Files selected for processing (3)
frontend/web/components/pages/environment-settings/tabs/warehouse-tab/ClickHouseConfigForm.tsxfrontend/web/components/pages/environment-settings/tabs/warehouse-tab/__tests__/clickhouseConfig.test.tsfrontend/web/components/pages/environment-settings/tabs/warehouse-tab/clickhouseConfig.ts
Visual Regression19 screenshots compared. See report for details. |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
frontend/web/components/pages/environment-settings/tabs/warehouse-tab/__tests__/clickhouseConfig.test.ts (1)
27-30: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick winCover invalid boundaries after trimming.
This test proves that
' 9440 'is accepted, but add cases such as' 0 'and' 65536 'to ensure trimming does not bypass the range checks.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 7fabd2ff-9263-47ab-943b-9fb7583ca9c4
📒 Files selected for processing (3)
frontend/web/components/pages/environment-settings/tabs/warehouse-tab/ClickHouseConfigForm.tsxfrontend/web/components/pages/environment-settings/tabs/warehouse-tab/__tests__/clickhouseConfig.test.tsfrontend/web/components/pages/environment-settings/tabs/warehouse-tab/clickhouseConfig.ts
33234e1 to
43faf52
Compare
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
Follow-ups to non-blocking review comments on #8028:
autocomplete="new-password"on the password input.How did you test this code?
Unit tests (
npm run test:unit -- --testPathPatterns=warehouse-tab), lint, typecheck. Manually: pasted values with trailing whitespace, invalid port, failed test.