PROD-WSF-001 — Hide or complete Search and Favorites
| Field | Value |
|---|---|
| Status | Open; source-verified |
| Severity | Medium |
| Components | sparqd/oqullus, sparqd/workspace-file-management-backend |
| Associated issues | Not opened |
Concrete observed case
The visible Search control filters only the currently loaded folder or Shared
array and resets on folder change. Oqullus defines but never calls the backend
workspace file-search endpoint. Favorite toggles modify only the current React
array; every fetch initializes isFavorite: false, and no backend favorite
model exists.
Expected condition
Either label search as Filter this folder and remove Favorites, or implement durable workspace-wide semantics with authorization, pagination, and refresh behavior.
Why it matters
Users can conclude a file does not exist because it is outside the current folder, and a saved-looking Favorite silently disappears after navigation.
Existing controls and workarounds
Navigate folders manually and treat Search as a current-folder filter. Do not rely on Favorites for durable organization.
Alternatives considered
- Recommended interim: rename Search to folder filter and hide Favorites.
- Implement server-side workspace search and per-user favorites.
- Browser persistence only — rejected because it is device-local and drifts across rename, delete, sharing, and workspace changes.
Component involvement
- Oqullus labels the current scope or consumes server search, and hides nonpersistent Favorites.
- The backend owns durable authorized search and favorites if those product capabilities are approved.
Reproduction and verification
Follow WSF-S009.
Resolution conditions
Close when the exposed labels match the implemented scope and state persists according to the documented contract.
Validation and blockers
Frontend behavior and the unused endpoint are source-confirmed. Product choice between a local filter and workspace-wide search remains open.