Summary 1. Load `channel_info` when editing: • Detect if the channel is in multi-key mode (`is_multi_key`). • Auto-initialize `batch`, `multiToSingle`, and `multiKeyMode` from backend data. 2. Visibility logic • Creation page: “Batch create / Multi-key mode” always available. • Edit page: show these controls **only when** the channel itself is multi-key. 3. State consistency • `multi_key_mode` added to `inputs`; `setValues(inputs)` now preserves the user’s selection. Result Single-key channels no longer display irrelevant “key aggregation” options, while multi-key channels open with the correct defaults, providing a cleaner and more accurate editing experience.
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| About | Loading commit data... | |
| Channel | Loading commit data... | |
| Chat | Loading commit data... | |
| Chat2Link | Loading commit data... | |
| Detail | Loading commit data... | |
| Home | Loading commit data... | |
| Log | Loading commit data... | |
| Midjourney | Loading commit data... | |
| NotFound | Loading commit data... | |
| Playground | Loading commit data... | |
| Pricing | Loading commit data... | |
| Redemption | Loading commit data... | |
| Setting | Loading commit data... | |
| Setup | Loading commit data... | |
| Task | Loading commit data... | |
| Token | Loading commit data... | |
| TopUp | Loading commit data... | |
| User | Loading commit data... |