fix(wren-ui): lint error

[fredalai]

Summary by CodeRabbit

• Style
  • Minor code formatting adjustments and whitespace cleanup for improved consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Minor code formatting improvements across two files: added a trailing comma in a constant set definition and removed stray blank lines from utility functions. No functional or logical changes.

Changes

Cohort / File(s)	Summary
Formatting & Whitespace Cleanup wren-ui/src/apollo/server/services/projectService.ts, wren-ui/src/hooks/useSetupConnectionDataSource.tsx	Added trailing comma to SENSITIVE_PROPERTY_NAME set; removed stray blank lines from transformFormToProperties and getAthenaAuthentication functions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

wren-ui

Suggested reviewers

• andreashimin
• douenergy

Poem

🐰 A comma tucked neatly in place,
blank lines vanish without a trace,
formatting clean, the code stands tall,
tiny tweaks that polish it all! ✨

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/lint-issue

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cbc8aa5 and 226c3b3.

📒 Files selected for processing (2)

• wren-ui/src/apollo/server/services/projectService.ts (1 hunks)
• wren-ui/src/hooks/useSetupConnectionDataSource.tsx (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}