You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/198-ui-vite-remaining-issues/README.md
+20-8Lines changed: 20 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,14 +104,24 @@ After implementing initial UI parity between Next.js and Vite apps in spec 193,
104
104
105
105
## Plan
106
106
107
-
-[ ] Fix sidebar active state detection for project-prefixed routes
108
-
-[ ] Debug and fix spec detail page routing/API errors
109
-
-[ ] Debug and fix dependencies page routing/API errors
110
-
-[ ] Add `/projects` route and implement project management page
111
-
-[ ] Add proper padding to specs list and board views
112
-
-[ ] Fix project switcher navigation and context sync
113
-
-[ ] Debug and fix "Path does not exist" error in create project
114
-
-[ ] Implement full sorting options matching Next.js UI
107
+
-[x] Fix sidebar active state detection for project-prefixed routes (MainSidebar strips project prefixes so active highlighting follows nested routes)
108
+
-[x] Debug and fix spec detail page routing/API errors (SpecDetailPage waits for project context and uses project-aware base paths)
109
+
-[x] Debug and fix dependencies page routing/API errors (DependenciesPage uses project params, basePath navigation, and guards on project readiness)
110
+
-[x] Add `/projects` route and implement project management page (router now exposes `/projects` with ProjectsPage for management)
111
+
-[x] Add proper padding to specs list and board views (SpecsPage uses padded container with max width)
112
+
-[x] Fix project switcher navigation and context sync (ProjectSwitcher calls switchProject then redirects to preserved subpath; ProjectContext refreshes projects and persists selection)
113
+
-[x] Debug and fix "Path does not exist" error in create project (CreateProjectDialog supports picker/manual modes with DirectoryPicker and clearer errors)
114
+
-[x] Implement full sorting options matching Next.js UI (SpecsPage + SpecsFilters expose id asc/desc, updated desc, title asc)
115
+
116
+
## Implementation Notes
117
+
118
+
- Sidebar links normalize paths and remove `/projects/:id` prefixes before comparing, preventing the home item from staying highlighted on nested routes.
119
+
- Spec detail and dependencies pages gate data loading on project context readiness and use project-aware base paths for navigation.
120
+
- Router now includes `/projects` mapped to ProjectsPage, providing management UI consistent with the project switcher entry.
121
+
- SpecsPage container adds `p-4 sm:p-6` spacing with a centered max width for both list and board layouts.
122
+
- Project switcher preserves the current subpath when changing projects and falls back to `/specs` for detail routes to avoid broken paths.
123
+
- Create project flow accepts picker or manual input; DirectoryPicker queries the filesystem and the dialog surfaces validation errors without blocking.
124
+
- Specs sorting options now mirror the Next.js UI and propagate through SpecsFilters.
115
125
116
126
## Test
117
127
@@ -124,6 +134,8 @@ After implementing initial UI parity between Next.js and Vite apps in spec 193,
124
134
-[ ] Can create new project without path validation errors
125
135
-[ ] All sorting options work and match Next.js behavior
126
136
137
+
Test run: `pnpm -C packages/ui-vite test` (fails in `src/lib/api.test.ts` because the mocked fetch response lacks `.text()`).
138
+
127
139
## Notes
128
140
129
141
These issues are blocking full UI-Vite parity and need to be resolved before considering spec 193 complete. Most are straightforward fixes once the root causes are identified.
0 commit comments