WIP: Dependency List - follow-up to preliminary frontend implementation
What does this MR do?
Finishes the remaining (client-side-only) frontend implementation for the Dependency List feature.
Why is MR this so large?
The Dependency List is a brand new feature for GitLab. It turned out it was perhaps too large to fit in one release cycle. What could be done during the %11.11 release cycle for the frontend happened in gitlab-org/gitlab-ee!11649. Unfortunately, that still remains unmerged, largely because it lacks the completion/polish that this MR hopefully brings.
Therefore, this MR is based on the feature branch for that old MR. The merge target of this MR is that base feature branch, rather than master, so that the final feature can be viewed holistically there once this one is merged.
I've split this MR as best as I could into logical commits, with detailed commit messages. So, reading through this MR commit-by-commit is probably the best way to review it.
Running this locally
TODO: Explain how
UX
TODO: add screenshots/video
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content