Add auto update setting

[heisbrot]

Summary by CodeRabbit

• New Features
  • Added automatic updates management to settings, allowing users to select between disabling updates, using the latest version, or specifying a custom version.
  • Introduced Save Changes functionality to persist update preferences to account settings.

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

[coderabbitai]

Walkthrough

The changes add automatic update version management to the Account interface and implement a new UI in the settings tab that allows users to select between Disabled, Latest, or Custom update versions, with validation and API integration for persisting changes.

Changes

Cohort / File(s)	Summary
Interface Enhancement src/interfaces/Account.ts	Added auto_update_version: string property to Account.settings.extra to support auto-update version configuration
Settings UI Implementation src/modules/settings/ClientSettingsTab.tsx	Introduced Automatic Updates UI block with dropdown selection (Disabled/Latest/Custom), custom version input field, version validation logic, state management for autoUpdateMethod and autoUpdateCustomVersion, and a saveChanges flow that updates account settings via API, refetches accounts, and updates the UI

Sequence Diagram

sequenceDiagram
    actor User
    participant UI as ClientSettingsTab
    participant API as Settings API
    participant Account as Account Service
    participant State as Component State

    User->>UI: Select auto-update option (Disabled/Latest/Custom)
    UI->>State: Update autoUpdateMethod state
    
    alt Custom Version Selected
        User->>UI: Enter custom version
        UI->>State: Validate & update autoUpdateCustomVersion
    end
    
    User->>UI: Click Save Changes
    UI->>API: POST updated account settings
    activate API
    API-->>UI: Success response
    deactivate API
    
    UI->>Account: Refetch accounts
    activate Account
    Account-->>UI: Updated account data
    deactivate Account
    
    UI->>State: Update UI with new values
    UI-->>User: Display confirmation

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• ClientSettingsTab.tsx requires careful review of state management logic, validation rules, and the saveChanges flow to ensure proper error handling and API integration
• Validation messaging implementation should be verified for correctness and edge cases
• Button enable/disable logic depends on changes, permissions, and validation state—verify all conditions are properly evaluated

Poem

🐰 A version selector hops into view,
Custom or latest, pick what's new!
Settings saved with a bounce and a bound,
Auto-updates make a joyful sound! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add auto update setting' directly describes the main changes: adding auto_update_version property to Account interface and implementing automatic updates UI in ClientSettingsTab.

✨ 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 feature/auto-update

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/modules/settings/ClientSettingsTab.tsx (1)

83-90: Consider removing the special case for "-".

The special case for "-" on line 86 appears intended to suppress errors during typing, but it's inconsistent—typing just "-" shows no error, but typing "0.52-" (mid-prerelease) still shows an error. Either debounce the validation or remove this edge case for consistency.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d6b617 and fd5822c.

📒 Files selected for processing (2)

• src/interfaces/Account.ts
• src/modules/settings/ClientSettingsTab.tsx

🧰 Additional context used

🧬 Code graph analysis (1)

src/modules/settings/ClientSettingsTab.tsx (4)

src/components/select/SelectDropdown.tsx (2)

• SelectOption (18-26)
• SelectDropdown (46-222)

src/utils/helpers.ts (1)

• validator (62-160)

src/components/Notification.tsx (1)

• notify (151-155)

src/components/HelpText.tsx (1)

• HelpText (9-25)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build_n_push

🔇 Additional comments (5)

src/interfaces/Account.ts (1)

25-25: LGTM!

The new auto_update_version property is correctly placed at the settings level, consistent with similar settings like lazy_connection_enabled.

Note: The AI summary incorrectly states this property is added to Account.settings.extra, but the actual placement at Account.settings level is correct based on the existing pattern.

src/modules/settings/ClientSettingsTab.tsx (4)

59-74: LGTM!

The state initialization logic correctly derives the initial UI state from the stored auto_update_version setting. The use of validator.isValidVersion() to distinguish between keyword values ("disabled"/"latest") and custom version strings is a clean approach.

---

110-128: LGTM!

The save logic correctly constructs the API value: custom version string when applicable, otherwise the method keyword ("disabled"/"latest"). The pattern follows the existing toggleLazyConnection implementation.

---

92-108: LGTM!

The save button enablement logic correctly gates saving when "Custom Version" is selected but no valid version is provided.

---

170-209: LGTM!

The UI implementation is clean:

• Save button correctly uses isSaveButtonDisabled and calls saveChanges
• Dropdown and input layout with conditional enabling is appropriate
• Input validation error display with tooltip provides good UX