Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !7883

Closed
Created Sep 27, 2014 by Administrator@rootOwner
  • Report abuse
Report abuse

[WIP] Factor blob and blame [failure unrelated]

  • Overview 11
  • Commits 1
  • Changes 5

Created by: cirosantilli

Philosophy: blame is just a type of view for a blob. There is even a toggle button to go between both.

This PR factors:

  • the filename holder on blame and blob views
  • controller logic for blame which is identical for blame by moving blame into the blob controller

It makes the following UI modifications which increases uniformity between blobs and blames:

  • show the branch / path breadcrumb and last commit to the top of the blame
  • remove the "blame view" title, since this is already obvious from the view itself, and from the "normal view" toggle button. Same rationale why the show view does not have a "Show view" title.

New:

screenshot from 2014-09-28 00 18 17 blob blame new

Old:

screenshot from 2014-09-28 00 18 32 blob blame old

We now have more functionality and uniformity with less lines of code.

TODO: the only implementation detail I'm not satisfied with is the route. Can anyone propose a shorter, DRYer way of writing it, possibly as a member of the :blob resource?

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/cirosantilli/factor-blob-blame