feat: connection groups with multi-selection and hierarchical management#140
Open
imhuytq wants to merge 24 commits intodatlechin:mainfrom
Open
feat: connection groups with multi-selection and hierarchical management#140imhuytq wants to merge 24 commits intodatlechin:mainfrom
imhuytq wants to merge 24 commits intodatlechin:mainfrom
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
imhuytq
force-pushed
the
feat/connection-groups
branch
from
c3497e9 to
e00e14e
Compare
Owner
|
Run bị lỗi rồi anh ơi |
# Conflicts: # TablePro/Models/DatabaseConnection.swift # TablePro/Views/WelcomeWindowView.swift
…search filter and keychain threading
Contributor
Author
|
@datlechin please review |
There was a problem hiding this comment.
Pull request overview
Adds a hierarchical “connection groups” feature to the welcome window, enabling nested folders for organizing database connections with expand/collapse persistence and drag-and-drop reordering.
Changes:
- Replaces the SwiftUI
Listconnection list with anNSOutlineView-backed tree view that supports nesting, drag/drop, and context menus. - Introduces a reusable group create/edit sheet and updates group pickers to support nested group selection.
- Extends storage/models to support group hierarchy (
parentGroupId), ordering (sortOrder), and persisted expanded state.
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| TablePro/Views/WelcomeWindowView.swift | Integrates group CRUD + expand state and swaps in the outline-based connection list. |
| TablePro/Views/WelcomeWindow/ConnectionOutlineView.swift | New NSOutlineView wrapper implementing hierarchy rendering, drag/drop reorder, and context menus. |
| TablePro/Views/Connection/ConnectionGroupPicker.swift | Updates the connection-form group picker to render nested groups and adds group management actions. |
| TablePro/Views/Connection/ConnectionGroupFormSheet.swift | New create/edit group sheet with color and parent-group selection (cycle prevention). |
| TablePro/Views/Connection/ConnectionFormView.swift | Minor update to reflect group support in form state (comment only in this diff). |
| TablePro/Resources/Localizable.xcstrings | Adds/removes localization keys used by new group UI. |
| TablePro/Models/DatabaseConnection.swift | Adds sortOrder to support stable ordering/reordering. |
| TablePro/Models/ConnectionGroup.swift | Adds hierarchy + ordering fields and migration-aware decoding. |
| TablePro/Core/Storage/GroupStorage.swift | Adds hierarchy helpers, expanded-state persistence, and descendant deletion behavior. |
| TablePro/Core/Storage/ConnectionStorage.swift | Persists sortOrder with migration fallback for pre-existing connections. |
| CHANGELOG.md | Documents the new “Connection groups” feature. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Owner
|
@imhuytq fix conflict lun nha a :d |
Contributor
Author
|
@datlechin review giúp với |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated 10 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- GroupStorage.addGroup returns Bool; duplicate check scoped to siblings - ConnectionGroupPicker delete now requires confirmation dialog - acceptGroupDrop adjusts childIndex for mixed group/connection children - isDragging set only after validation passes in drag source - totalConnectionCount guards against circular parentGroupId cycles - duplicateConnection returns placed copy with correct sortOrder - 2-step delete step2 only shown for group-resident connections - Remove duplicated collectDescendantIds; reuse GroupStorage method - Remove unnecessary comments in WelcomeWindowView
imhuytq
changed the title
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 14 out of 14 changed files in this pull request and generated 7 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
datlechin
force-pushed
the
feat/connection-groups
branch
from
5620545 to
864f32a
Compare
Owner
Em chạy lên thấy màu active hình như bị nhạt hơn so với bình thường
|
# Conflicts: # TablePro/Core/Storage/ConnectionStorage.swift # TablePro/Models/DatabaseConnection.swift # TablePro/Resources/Localizable.xcstrings # TablePro/Views/Connection/ConnectionGroupPicker.swift # TablePro/Views/Connection/WelcomeWindowView.swift
Contributor
|
Thank you for your contribution! Before we can merge this PR, you need to sign our Contributor License Agreement. To sign, please comment below with:
I have read the CLA Document and I hereby sign the CLA. You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
📝 WalkthroughWalkthroughThis PR introduces a connection groups feature enabling hierarchical organization of database connections into color-coded folders with sorting, persist expanded/collapsed states, and connection ordering. Data models are extended with parent-child relationships and sort orders across storage and view layers. Documentation updated with download instructions. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (3)
docs/docs.json (1)
220-226: Consider adding Chinese download page for consistency.The English (line 29) and Vietnamese (line 124) Getting Started sections now include
download, but the Chinese section does not havezh/download. If Chinese documentation should maintain parity, consider adding it here or tracking it for future work.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/docs.json` around lines 220 - 226, The Chinese "快速开始" section in docs.json is missing the zh/download entry; update the pages array for the group "快速开始" to include "zh/download" alongside "zh/index", "zh/quickstart", "zh/installation", and "zh/changelog" so the Chinese docs mirror the English and Vietnamese Getting Started sections.docs/download.mdx (1)
35-35: Apple logo character may not render universally.The Apple logo character (``) in "Apple menu ()" relies on Apple-specific fonts and may display as a missing glyph on non-Apple devices or certain browsers. Consider using "Apple menu" without the symbol, or add fallback text like "Apple menu (Apple icon)".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/download.mdx` at line 35, Replace the Apple logo glyph in the string "Click the **Apple menu** () > **About This Mac**:" with either plain text or a fallback label; specifically update the phrase "Apple menu ()" to "Apple menu" or "Apple menu (Apple icon)" so the documentation doesn't rely on an Apple-specific glyph that may not render on all devices.docs/vi/download.mdx (1)
35-35: Same Apple logo rendering concern applies here.As noted in the English version, the Apple logo character (``) may not render on non-Apple devices.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/vi/download.mdx` at line 35, The Apple logo character in the sentence "Nhấp vào **menu Apple** () > **Giới thiệu về máy Mac này**" may not render on non‑Apple devices; update that fragment (the "menu Apple" line) to use a visible, accessible fallback instead of relying on the single logo glyph—either replace the empty parentheses with the word "Apple" (e.g., "menu Apple (Apple logo)"), or replace the glyph with an inline image/SVG that includes appropriate alt text, matching the approach used in the English doc to ensure correct rendering and accessibility.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 239: The changelog entry "Connection groups: organize connections into
named, color-coded folders with support for nested subgroups, drag-and-drop
reordering, expand/collapse state persistence, multi-selection (bulk delete,
bulk move to group), and context menus for group and connection management"
should be removed from the "## [0.14.1]" section and added under "##
[Unreleased]" inside the "### Added" subsection; locate that exact entry text in
CHANGELOG.md, cut it from the 0.14.1 section and paste it as a new bullet under
the Unreleased -> Added heading so the feature is tracked as unreleased.
In `@TablePro/Core/Storage/GroupStorage.swift`:
- Around line 100-115: When removing connections in the Group deletion loop,
ensure you both clean TOTP secrets and record deletions with the sync tracker:
for each conn where you currently call storage.deletePassword(for:),
storage.deleteSSHPassword(for:) and storage.deleteKeyPassphrase(for:), also call
storage.deleteTOTPSecret(for: conn.id) and notify the sync system (e.g.
SyncChangeTracker.shared.recordDeletion(for: conn.id) or the appropriate method
on SyncChangeTracker) so a tombstone/change is recorded before calling
storage.saveConnections(remaining).
- Around line 177-183: The recursive helper collectDescendantIds(of:in:) lacks
cycle protection; modify it to track visited nodes (e.g., add an inout Set<UUID>
visited parameter or create a private helper
collectDescendantIds(of:in:visited:)) and on entry check/mark the current
groupId in visited so you skip already-seen IDs before filtering children or
recursing; ensure you still accumulate child IDs into result but avoid recursing
into a child whose id is in visited to prevent infinite recursion on malformed
cycles.
In `@TablePro/Views/Connection/ConnectionFormView.swift`:
- Around line 1056-1059: The code unconditionally copies
savedConnections[index].sortOrder into updated.sortOrder which breaks ordering
when the user changed connectionToSave.groupId; instead, check if
connectionToSave.groupId == savedConnections[index].groupId and only preserve
updated.sortOrder in that case, otherwise assign a new sortOrder appropriate for
the target group (e.g., compute max sortOrder among savedConnections with the
new groupId and set updated.sortOrder = max + 1 or nil as your model requires)
before replacing savedConnections[index]; update the logic around
connectionToSave, updated.sortOrder, and savedConnections to implement this
conditional behavior.
---
Nitpick comments:
In `@docs/docs.json`:
- Around line 220-226: The Chinese "快速开始" section in docs.json is missing the
zh/download entry; update the pages array for the group "快速开始" to include
"zh/download" alongside "zh/index", "zh/quickstart", "zh/installation", and
"zh/changelog" so the Chinese docs mirror the English and Vietnamese Getting
Started sections.
In `@docs/download.mdx`:
- Line 35: Replace the Apple logo glyph in the string "Click the **Apple menu**
() > **About This Mac**:" with either plain text or a fallback label;
specifically update the phrase "Apple menu ()" to "Apple menu" or "Apple menu
(Apple icon)" so the documentation doesn't rely on an Apple-specific glyph that
may not render on all devices.
In `@docs/vi/download.mdx`:
- Line 35: The Apple logo character in the sentence "Nhấp vào **menu Apple** ()
> **Giới thiệu về máy Mac này**" may not render on non‑Apple devices; update
that fragment (the "menu Apple" line) to use a visible, accessible fallback
instead of relying on the single logo glyph—either replace the empty parentheses
with the word "Apple" (e.g., "menu Apple (Apple logo)"), or replace the glyph
with an inline image/SVG that includes appropriate alt text, matching the
approach used in the English doc to ensure correct rendering and accessibility.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c79d7f7a-9262-4047-808d-0c6c0455f6c5
📒 Files selected for processing (9)
CHANGELOG.mdTablePro/Core/Storage/ConnectionStorage.swiftTablePro/Core/Storage/GroupStorage.swiftTablePro/Models/Connection/ConnectionGroup.swiftTablePro/Models/Connection/DatabaseConnection.swiftTablePro/Views/Connection/ConnectionFormView.swiftdocs/docs.jsondocs/download.mdxdocs/vi/download.mdx
|
|
||
| ### Added | ||
|
|
||
| - Connection groups: organize connections into named, color-coded folders with support for nested subgroups, drag-and-drop reordering, expand/collapse state persistence, multi-selection (bulk delete, bulk move to group), and context menus for group and connection management |
There was a problem hiding this comment.
Move this entry to [Unreleased] instead of [0.14.1].
Line 239 documents a new feature in a historical release section. This should be listed under ## [Unreleased] (### Added) until release.
📘 Suggested changelog placement
## [Unreleased]
+
+### Added
+
+- Connection groups: organize connections into named, color-coded folders with support for nested subgroups, drag-and-drop reordering, expand/collapse state persistence, multi-selection (bulk delete, bulk move to group), and context menus for group and connection management
## [0.14.1] - 2026-03-06
### Added
-- Connection groups: organize connections into named, color-coded folders with support for nested subgroups, drag-and-drop reordering, expand/collapse state persistence, multi-selection (bulk delete, bulk move to group), and context menus for group and connection management
- Add database and schema switching for PostgreSQL connections via ⌘KAs per coding guidelines: "Update CHANGELOG.md under [Unreleased] section (Added/Fixed/Changed) for new features and notable changes."
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - Connection groups: organize connections into named, color-coded folders with support for nested subgroups, drag-and-drop reordering, expand/collapse state persistence, multi-selection (bulk delete, bulk move to group), and context menus for group and connection management | |
| ## [Unreleased] | |
| ### Added | |
| - Connection groups: organize connections into named, color-coded folders with support for nested subgroups, drag-and-drop reordering, expand/collapse state persistence, multi-selection (bulk delete, bulk move to group), and context menus for group and connection management | |
| ## [0.14.1] - 2026-03-06 | |
| ### Added | |
| - Add database and schema switching for PostgreSQL connections via ⌘K |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` at line 239, The changelog entry "Connection groups: organize
connections into named, color-coded folders with support for nested subgroups,
drag-and-drop reordering, expand/collapse state persistence, multi-selection
(bulk delete, bulk move to group), and context menus for group and connection
management" should be removed from the "## [0.14.1]" section and added under "##
[Unreleased]" inside the "### Added" subsection; locate that exact entry text in
CHANGELOG.md, cut it from the 0.14.1 section and paste it as a new bullet under
the Unreleased -> Added heading so the feature is tracked as unreleased.
Comment on lines
+100
to
+115
| // Delete connections that belonged to deleted groups | ||
| let storage = ConnectionStorage.shared | ||
| let connections = storage.loadConnections() | ||
| var remaining: [DatabaseConnection] = [] | ||
| for conn in connections { | ||
| if let gid = conn.groupId, allDeletedIds.contains(gid) { | ||
| // Clean up keychain entries | ||
| storage.deletePassword(for: conn.id) | ||
| storage.deleteSSHPassword(for: conn.id) | ||
| storage.deleteKeyPassphrase(for: conn.id) | ||
| } else { | ||
| remaining.append(conn) | ||
| } | ||
| } | ||
| storage.saveConnections(remaining) | ||
| } |
There was a problem hiding this comment.
Group deletion misses connection tombstones and TOTP keychain cleanup.
In Lines 105–114, deleted connections are removed from persisted data, but:
SyncChangeTrackeris not notified for each deleted connection.deleteTOTPSecret(for:)is not called.
This can leave stale synced records and orphaned secrets.
🛠️ Suggested fix
for conn in connections {
if let gid = conn.groupId, allDeletedIds.contains(gid) {
+ SyncChangeTracker.shared.markDeleted(.connection, id: conn.id.uuidString)
// Clean up keychain entries
storage.deletePassword(for: conn.id)
storage.deleteSSHPassword(for: conn.id)
storage.deleteKeyPassphrase(for: conn.id)
+ storage.deleteTOTPSecret(for: conn.id)
} else {
remaining.append(conn)
}
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| // Delete connections that belonged to deleted groups | |
| let storage = ConnectionStorage.shared | |
| let connections = storage.loadConnections() | |
| var remaining: [DatabaseConnection] = [] | |
| for conn in connections { | |
| if let gid = conn.groupId, allDeletedIds.contains(gid) { | |
| // Clean up keychain entries | |
| storage.deletePassword(for: conn.id) | |
| storage.deleteSSHPassword(for: conn.id) | |
| storage.deleteKeyPassphrase(for: conn.id) | |
| } else { | |
| remaining.append(conn) | |
| } | |
| } | |
| storage.saveConnections(remaining) | |
| } | |
| // Delete connections that belonged to deleted groups | |
| let storage = ConnectionStorage.shared | |
| let connections = storage.loadConnections() | |
| var remaining: [DatabaseConnection] = [] | |
| for conn in connections { | |
| if let gid = conn.groupId, allDeletedIds.contains(gid) { | |
| SyncChangeTracker.shared.markDeleted(.connection, id: conn.id.uuidString) | |
| // Clean up keychain entries | |
| storage.deletePassword(for: conn.id) | |
| storage.deleteSSHPassword(for: conn.id) | |
| storage.deleteKeyPassphrase(for: conn.id) | |
| storage.deleteTOTPSecret(for: conn.id) | |
| } else { | |
| remaining.append(conn) | |
| } | |
| } | |
| storage.saveConnections(remaining) | |
| } |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@TablePro/Core/Storage/GroupStorage.swift` around lines 100 - 115, When
removing connections in the Group deletion loop, ensure you both clean TOTP
secrets and record deletions with the sync tracker: for each conn where you
currently call storage.deletePassword(for:), storage.deleteSSHPassword(for:) and
storage.deleteKeyPassphrase(for:), also call storage.deleteTOTPSecret(for:
conn.id) and notify the sync system (e.g.
SyncChangeTracker.shared.recordDeletion(for: conn.id) or the appropriate method
on SyncChangeTracker) so a tombstone/change is recorded before calling
storage.saveConnections(remaining).
Comment on lines
+177
to
+183
| func collectDescendantIds(of groupId: UUID, in groups: [ConnectionGroup]) -> Set<UUID> { | ||
| var result = Set<UUID>() | ||
| let children = groups.filter { $0.parentGroupId == groupId } | ||
| for child in children { | ||
| result.insert(child.id) | ||
| result.formUnion(collectDescendantIds(of: child.id, in: groups)) | ||
| } |
There was a problem hiding this comment.
Descendant traversal needs cycle protection.
collectDescendantIds (Lines 177–183) recursively follows parent links with no visited-set guard. A malformed cycle can recurse indefinitely and crash delete/count flows.
🛡️ Suggested fix
- func collectDescendantIds(of groupId: UUID, in groups: [ConnectionGroup]) -> Set<UUID> {
- var result = Set<UUID>()
- let children = groups.filter { $0.parentGroupId == groupId }
- for child in children {
- result.insert(child.id)
- result.formUnion(collectDescendantIds(of: child.id, in: groups))
- }
- return result
- }
+ private func collectDescendantIds(of groupId: UUID, in groups: [ConnectionGroup]) -> Set<UUID> {
+ var visited: Set<UUID> = []
+ return collectDescendantIds(of: groupId, in: groups, visited: &visited)
+ }
+
+ private func collectDescendantIds(
+ of groupId: UUID,
+ in groups: [ConnectionGroup],
+ visited: inout Set<UUID>
+ ) -> Set<UUID> {
+ guard visited.insert(groupId).inserted else { return [] }
+ var result = Set<UUID>()
+ let children = groups.filter { $0.parentGroupId == groupId }
+ for child in children {
+ result.insert(child.id)
+ result.formUnion(collectDescendantIds(of: child.id, in: groups, visited: &visited))
+ }
+ return result
+ }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@TablePro/Core/Storage/GroupStorage.swift` around lines 177 - 183, The
recursive helper collectDescendantIds(of:in:) lacks cycle protection; modify it
to track visited nodes (e.g., add an inout Set<UUID> visited parameter or create
a private helper collectDescendantIds(of:in:visited:)) and on entry check/mark
the current groupId in visited so you skip already-seen IDs before filtering
children or recursing; ensure you still accumulate child IDs into result but
avoid recursing into a child whose id is in visited to prevent infinite
recursion on malformed cycles.
Comment on lines
+1056
to
+1059
| // Preserve sortOrder from existing connection | ||
| var updated = connectionToSave | ||
| updated.sortOrder = savedConnections[index].sortOrder | ||
| savedConnections[index] = updated |
There was a problem hiding this comment.
Preserving sortOrder unconditionally breaks cross-group edits.
At Line 1058, updated.sortOrder is always copied from the old record. If the user changed groupId, this reuses an order from a different sibling set and can cause ordering collisions.
🔧 Suggested fix
if let index = savedConnections.firstIndex(where: { $0.id == connectionToSave.id }) {
- // Preserve sortOrder from existing connection
var updated = connectionToSave
- updated.sortOrder = savedConnections[index].sortOrder
+ let previous = savedConnections[index]
+ if previous.groupId == updated.groupId {
+ updated.sortOrder = previous.sortOrder
+ } else {
+ let nextSortOrder = (
+ savedConnections
+ .filter { $0.id != updated.id && $0.groupId == updated.groupId }
+ .map(\.sortOrder)
+ .max() ?? -1
+ ) + 1
+ updated.sortOrder = nextSortOrder
+ }
savedConnections[index] = updated
storage.saveConnections(savedConnections)
SyncChangeTracker.shared.markDirty(.connection, id: connectionToSave.id.uuidString)
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| // Preserve sortOrder from existing connection | |
| var updated = connectionToSave | |
| updated.sortOrder = savedConnections[index].sortOrder | |
| savedConnections[index] = updated | |
| var updated = connectionToSave | |
| let previous = savedConnections[index] | |
| if previous.groupId == updated.groupId { | |
| updated.sortOrder = previous.sortOrder | |
| } else { | |
| let nextSortOrder = ( | |
| savedConnections | |
| .filter { $0.id != updated.id && $0.groupId == updated.groupId } | |
| .map(\.sortOrder) | |
| .max() ?? -1 | |
| ) + 1 | |
| updated.sortOrder = nextSortOrder | |
| } | |
| savedConnections[index] = updated |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@TablePro/Views/Connection/ConnectionFormView.swift` around lines 1056 - 1059,
The code unconditionally copies savedConnections[index].sortOrder into
updated.sortOrder which breaks ordering when the user changed
connectionToSave.groupId; instead, check if connectionToSave.groupId ==
savedConnections[index].groupId and only preserve updated.sortOrder in that
case, otherwise assign a new sortOrder appropriate for the target group (e.g.,
compute max sortOrder among savedConnections with the new groupId and set
updated.sortOrder = max + 1 or nil as your model requires) before replacing
savedConnections[index]; update the logic around connectionToSave,
updated.sortOrder, and savedConnections to implement this conditional behavior.
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
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
Adds a hierarchical connection groups system to the welcome window, letting users organize database connections into named, color-coded folders with arbitrary nesting depth.
Core features
ListwithNSOutlineViewfor native tree view, expand/collapse, and drag-and-dropData model changes
ConnectionGroup: new model withparentGroupIdfor nesting,sortOrder, andcolorDatabaseConnection.sortOrder: new field for stable ordering within groupsGroupStorage: CRUD, hierarchy helpers, expanded state persistence, descendant deletion with connection cleanupsortOrderwhen upgrading from older versions without orderingStorage behavior
ConnectionStorage.duplicateConnectionpreserves all fields and inserts right after the originalConnectionFormViewpreservessortOrderwhen editing existing connectionsUI/UX details
Summary by CodeRabbit
Release Notes
New Features
Documentation