Switch Package Registry breadcrumbs to use singleNavOptIn

Thomas Huttererrequested to merge
539583-package-registry into master

What does this MR do and why?

Switches Package Registry and Container Registry breadcrumbs to use the new singleNavOptIn approach.

We are migrating all pages that use the injectVueAppBreadcrumbs mechanism to this new approach. Later, when all pages will be migrated, we'll remove the old code path (singleNavOptIn on false).

References

Part of #539583 (closed)

Screenshots or screen recordings

Package Registry

👉 http://gdk.test:3000/flightjs/Flight/-/packages/26

image

Container Registry

👉 http://gdk.test:3000/flightjs/Flight/container_registry/1

image

How to set up and validate locally

  • Inspect the page breadcrumbs with your Vue dev tools on the affected pages (See screenshot section for links)
  • The breadcrumbs (incl Group/project) are all in one single GlBreadcrumb component.
  • Compare to master, where you find two GlBreadcrumb instances next to each other.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #539583 (closed)

Edited by Thomas Hutterer

Merge request reports