Content
View differences
Updated by Jens Ulferts over 10 years ago
Currently, a work package’s activities are loaded together with the work package. This applies to the front-end as well as the back end. But loading all of this at once, especially since loading the activities is slow and the complexity for doing it is O (n), we need to decouple the two.
**Acceptance criteria**
- APIv3 work\_packages\#show no longer embeds the activities
- The `work_packages/:id/activity` (and `project/:project_id/work_packages/details/:id/overview`) displays the work package overview information (the work package’s primary information) first. It then loads the activities in a separate request. There should be some indicator of progress (e.g. spinner) at the place where the activities will be rendered.
- The separation also works on work package creation and update.
**Acceptance criteria**
- APIv3 work\_packages\#show no longer embeds the activities
- The `work_packages/:id/activity` (and `project/:project_id/work_packages/details/:id/overview`) displays the work package overview information (the work package’s primary information) first. It then loads the activities in a separate request. There should be some indicator of progress (e.g. spinner) at the place where the activities will be rendered.
- The separation also works on work package creation and update.