admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: separate server deployment mode inputs

Browse Source
This commit is contained in:
npc0-hue
2026-07-24 19:38:46 +08:00
parent ab943536b0
commit 6cfd929f7f
7 changed files with 24 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/redesign-server-deployment-workflow/design.md
+1 -1
View File
@@ -31,7 +31,7 @@ The alternative—incrementally rearranging the two current forms—would keep d
The component has four steps: target (plugin plus Run or explicit draft), deployment method, configuration, and review. Forward navigation validates only fields required by the selected mode. Back navigation preserves typed values. The final review is the only submit point.
`guided-install` shows plugin game inputs and a primary “server directory”; `existing-server` shows the existing server directory; `custom-command` adds launch data. `workingDirectory` is an advanced custom-command input labelled as an execution directory and defaults logically to `serverRoot` when omitted. This preserves the current protocol distinction without demanding it from normal users.
`guided-install` shows plugin game inputs and an optional “installation directory”; `existing-server` requires an “existing server directory” and explicitly states that it will not reinstall or overwrite game configuration; `custom-command` adds launch data. `workingDirectory` is an advanced custom-command input labelled as an execution directory and defaults logically to `serverRoot` when omitted. This preserves the current protocol distinction without demanding it from normal users.
### 3. Draft is a deliberate outcome