aglinxinyuan opened a new issue, #7460:
URL: https://github.com/apache/texera/issues/7460

   ### Task Summary
   
   Remove the deprecated **project** feature (a colour-tagged collection of 
workflows, with sharing and public projects) from the Angular frontend.
   
   Consensus to remove was reached in #5172 — the feature was hidden behind 
`projects_enabled = false` in #3343 (2025-04-02) and has been unmaintained 
since. This issue covers the frontend half; the backend and schema half is 
tracked separately.
   
   ```
   project feature
   ├── frontend  ← this issue
   └── backend + DB schema  ← separate issue
   ```
   
   **Scope**
   
   | Area | What goes |
   | --- | --- |
   | Components | the whole `dashboard/component/user/user-project/` tree — 
list page, section page, list item, public-project modal, add/remove-workflow 
modals |
   | Services | `UserProjectService`, `StubUserProjectService`, 
`PublicProjectService` |
   | Types | `DashboardProject` / `PublicProject`, the `project` member of 
`SearchResult`, `isDashboardProject` |
   | Routing | the `user/project` and `user/project/:pid` routes and the 
`USER_PROJECT` path constant |
   | Config | the `projects_enabled` field of `SidebarTabs`, the sidebar tab, 
and the admin-settings toggle |
   | Search / filters | project filter chips, `projectIds` search params, the 
project branch of the entry builder |
   | Module wiring | the six `app.module.ts` declarations and their imports |
   
   **Out of scope** — the `Projection` operator, sbt `project/` directories, 
and anything else merely containing the word "project".
   
   The backend keeps serving `/project` for now, so this PR is safe to land on 
its own: the endpoints simply stop being called.
   
   ### Task Type
   
   - [x] Refactor / Cleanup
   - [ ] DevOps / Deployment / CI
   - [ ] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to