starred/EasyCLI

Fork 0

mirror of https://github.com/router-for-me/EasyCLI.git synced 2026-04-25 07:35:51 +03:00

[PR #10] [MERGED] feat: add configurable request timeout setting #28

New issue

Closed

opened 2026-02-27 16:46:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 16:46:49 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/router-for-me/EasyCLI/pull/10
Author: @benzntech
Created: 10/24/2025
Status: ✅ Merged
Merged: 10/25/2025
Merged by: @luispater

Base: main ← Head: feature/add-timeout-setting

📝 Commits (2)

3516412 feat: automatically cleanup old CLIProxyAPI versions during update
6a633d7 feat: add configurable request timeout setting

📊 Changes

3 files changed (+35 additions, -1 deletions)

View changed files

📝 js/settings-core.js (+7 -0)
📝 settings.html (+9 -0)
📝 src-tauri/src/main.rs (+19 -1)

📄 Description

Description

This PR adds a new configurable request timeout setting to the EasyCLI settings UI, allowing users to customize the timeout duration for API requests.

Changes

Added "Request Timeout" input field in the Basic Settings section
Configurable range: 30-600 seconds
Default value: 120 seconds (matches CLIProxyAPI default)
Integrated with the existing config management system
Value syncs with server configuration and updates on apply

UI Changes

New setting appears in the Basic Settings section below "Request Retry":

Label: "Request Timeout"
Description: "Request timeout in seconds (default: 120)"
Input type: Number with min=30, max=600

Benefits

Gives users control over request timeout behavior
Useful for slower network connections or API endpoints
Helps prevent premature timeout errors on legitimate long-running requests
Maintains reasonable bounds (30s min, 600s max) to prevent misconfigurations

Testing

Setting value persists correctly in config
Default value (120s) loads properly on first launch
Changes sync with server configuration
Value validation ensures within acceptable range

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/router-for-me/EasyCLI/pull/10 **Author:** [@benzntech](https://github.com/benzntech) **Created:** 10/24/2025 **Status:** ✅ Merged **Merged:** 10/25/2025 **Merged by:** [@luispater](https://github.com/luispater) **Base:** `main` ← **Head:** `feature/add-timeout-setting` --- ### 📝 Commits (2) - [`3516412`](https://github.com/router-for-me/EasyCLI/commit/3516412c4f90024aaf6afb350c053f62a93abb50) feat: automatically cleanup old CLIProxyAPI versions during update - [`6a633d7`](https://github.com/router-for-me/EasyCLI/commit/6a633d769901ae5203726a606e0493c08e6f4c0c) feat: add configurable request timeout setting ### 📊 Changes **3 files changed** (+35 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `js/settings-core.js` (+7 -0) 📝 `settings.html` (+9 -0) 📝 `src-tauri/src/main.rs` (+19 -1) </details> ### 📄 Description ## Description This PR adds a new configurable request timeout setting to the EasyCLI settings UI, allowing users to customize the timeout duration for API requests. ## Changes - Added "Request Timeout" input field in the Basic Settings section - Configurable range: 30-600 seconds - Default value: 120 seconds (matches CLIProxyAPI default) - Integrated with the existing config management system - Value syncs with server configuration and updates on apply ## UI Changes New setting appears in the Basic Settings section below "Request Retry": - Label: "Request Timeout" - Description: "Request timeout in seconds (default: 120)" - Input type: Number with min=30, max=600 ## Benefits - Gives users control over request timeout behavior - Useful for slower network connections or API endpoints - Helps prevent premature timeout errors on legitimate long-running requests - Maintains reasonable bounds (30s min, 600s max) to prevent misconfigurations ## Testing - Setting value persists correctly in config - Default value (120s) loads properly on first launch - Changes sync with server configuration - Value validation ensures within acceptable range --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-27 16:46:49 +03:00

closed this issue
added the
pull-request
label

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/EasyCLI#28

No description provided.

Rows
Columns