Skip to content

Remove "subscribed" field from API responses returning list of issues or merge requests

Adam Niedzielski requested to merge api-drop-subscribed into master

What does this MR do?

It removes subscribed field from our API V4 responses where we return a list of issues or merge requests. It introduces Entities::IssueBasic and Entities::MergeRequestBasic that do not contain subscribed field.

Why was this MR needed?

Calculating the value of subscribed field triggers Markdown processing (as described in https://gitlab.com/gitlab-org/gitlab-ce/issues/22374). We can't do that for multiple issues / merge requests in a single API request.

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/22374

Merge request reports