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

   Follow-up from PR #5704 review.
   
   ### Problem
   Each workflow card calls `GET /{wid}/cover` individually 
(`WorkflowCoverService.getCover`), so a dashboard/hub page of N cards issues N 
separate requests, each a DB hit plus an access check. This will scale poorly 
on a busy dashboard.
   
   PR #5704 already fixed the per-card correctness issues (stale-cover flash 
and out-of-order resolution via `switchMap` + eager reset), but the fetch 
volume remains.
   
   ### Proposal
   Fold a `hasCover` flag (or the cover data itself) into the existing 
workflow-list/search payload so cards can either render directly or gate a lazy 
fetch, instead of every card fetching unconditionally on init.
   
   This touches the workflow-list/search query and response type, which is why 
it was deferred out of #5704.
   
   ### Context
   - Service: 
`frontend/src/app/dashboard/service/user/workflow-cover/workflow-cover.service.ts`
   - Consumer: 
`frontend/src/app/dashboard/component/user/list-item/card-item/card-item.component.ts`
   - Backend endpoint: `WorkflowResource.getCoverImage`


-- 
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