fix: allow configuration editing on failed workspaces

tylerpotts · tylerpotts · commit 516aab454468 · 2026-04-27T15:46:29.000-05:00
The Configuration tab was gated behind a `status === 'ready'` check,
which blocked users from viewing or editing pixi.toml when a workspace
failed during initial creation. This made it impossible to fix a broken
configuration without recreating the workspace from scratch.

The backend (GetPixiToml / SavePixiToml) already supports reading and
writing pixi.toml regardless of workspace status, so this was purely a
frontend restriction. Removed the status guard from three places:

- useEffect that loads toml content when switching to the tab
- disabled prop on the Edit button in the workspace header
- conditional block that replaced the editor with a "must be ready" message
diff --git a/frontend/src/pages/WorkspaceDetail.tsx b/frontend/src/pages/WorkspaceDetail.tsx
@@ -65,7 +65,7 @@ export const WorkspaceDetail = () => {
 
   // Load pixi.toml when switching to that tab
   useEffect(() => {
-    if (activeTab === 'toml' && !pixiToml && workspace?.status === 'ready') {
+    if (activeTab === 'toml' && !pixiToml) {
       loadPixiToml();
     }
   }, [activeTab, workspace?.status]);
@@ -162,7 +162,6 @@ export const WorkspaceDetail = () => {
             variant="outline"
             size="sm"
             className="gap-2"
-            disabled={workspace.status !== 'ready'}
             onClick={async () => {
               if (!pixiToml) {
                 setLoadingToml(true);
@@ -527,11 +526,7 @@ export const WorkspaceDetail = () => {
                 )}
               </div>
             </div>
-            {workspace.status !== 'ready' ? (
-              <div className="text-center py-8 text-muted-foreground">
-                Workspace must be ready to view pixi.toml
-              </div>
-            ) : loadingToml ? (
+            {loadingToml ? (
               <div className="flex items-center justify-center py-12">
                 <Loader2 className="h-8 w-8 animate-spin text-muted-foreground" />
               </div>
