建议【批量编辑】中增加其他参数的批量设置

[sk163]

目前批量编辑中仅能批量设置：状态、优先级、权重、价格倍率、分组标签等，希望增加如：熔断器配置、超时配置等参数

[github-actions]

Thank you for this feature suggestion.

Feasibility assessment:

This is a reasonable enhancement request. The current batch edit functionality for providers supports the following fields:

• Status (is_enabled)
• Priority (priority)
• Weight (weight)
• Cost multiplier (cost_multiplier)
• Group tag (group_tag)

Related existing code:

• src/app/[locale]/settings/providers/_components/batch-edit/provider-batch-dialog.tsx (lines 47-71) - Defines the EditFieldState interface with the current batch-editable fields
• src/actions/providers.ts (lines 1006-1014) - Defines BatchUpdateProvidersParams interface that specifies which fields can be batch updated
• src/drizzle/schema.ts (lines 230-256) - Provider schema includes the circuit breaker and timeout fields you mentioned:
  • Circuit breaker: maxRetryAttempts, circuitBreakerFailureThreshold, circuitBreakerOpenDuration, circuitBreakerHalfOpenSuccessThreshold
  • Timeout: firstByteTimeoutStreamingMs, streamingIdleTimeoutMs, requestTimeoutNonStreamingMs

Implementation considerations:

1. The UI component (provider-batch-dialog.tsx) would need new field toggles and inputs for circuit breaker and timeout settings
2. The BatchUpdateProvidersParams interface in src/actions/providers.ts would need to be extended to include these additional fields
3. The repository layer (updateProvidersBatch) would need to handle the new fields
4. Input validation would be needed (e.g., timeout values must be non-negative integers, circuit breaker thresholds must be positive)

Dependencies:

• src/app/[locale]/settings/providers/_components/batch-edit/ - UI components
• src/actions/providers.ts - Server actions
• src/repository/provider.ts - Data access layer

---

Automated response from Claude AI

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the last 30 days.

If this issue is still relevant:

• Please comment to keep it open
• Add any new information that might help resolve it

This issue will be automatically closed in 14 days if there is no further activity.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the last 30 days.

If this issue is still relevant:

• Please comment to keep it open
• Add any new information that might help resolve it

This issue will be automatically closed in 14 days if there is no further activity.

[github-actions]

This issue has been automatically closed due to inactivity.

If you believe this issue is still relevant, please feel free to reopen it with additional information.