<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=329845) </details> <!--IssueSummary end--> In the MR Conflict Resolver App we are iterating over a list of files, [the template is about 50 lines long](https://gitlab.com/gitlab-org/gitlab/-/blob/dd985dc68ce6e3404d8ba97fae4650b6a7f5a3de/app/assets/javascripts/merge_conflicts/merge_conflict_resolver_app.vue#L113-167) and has some logic that could be made more readable by introducing a separate component utilizing computed props and such. - - - The following discussion from !59400 should be addressed: - [ ] @justin_ho started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/59400#note_554491591): (+2 comments) > Suggestion (non-blocking): Looking at how these checks are repeated a few times, maybe we can add some computed props that return these values. For example, `isResolveModeInteractive` or `isTypeText`.