Navigation bar customization

[davidwaroquiers]

This PR implements the first phase of configurable navigation described in the corresponding issue: #2035

Deployments can now configure the visible views, their order, labels, and optional icons through NAVIGATION in config.json or PYDATALAB_NAVIGATION.

Existing deployments retain the current navigation by default.

The backend exposes this configuration through /info, and the frontend resolves stable view IDs through a central view catalog.

Future phases
A later phase will extend the same approach to support:

• Complete custom Vue views
• Generated item table views for one or more item types

The same registry-based approach also provides a path towards a dedicated data blocks view, now that blocks are stored in their own collection (#2069 ).

Example of a customized nav bar with the following NAVIGATION in config.json:

{
  "NAVIGATION": [
    {
      "view": "samples"
    },
    {
      "view": "starting-materials",
      "label": "Starting Materials",
      "icon": "vials"
    },
    {
      "view": "equipment"
    },
    {
      "view": "item-graph",
      "label": "Graph View",
      "icon": "project-diagram"
    },
    {
      "view": "about"
    }
  ]
}

[codecov]

Codecov Report

❌ Patch coverage is 97.14286% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 82.56%. Comparing base (ddb057c) to head (c06f5be).

Files with missing lines	Patch %	Lines
pydatalab/src/pydatalab/config.py	96.96%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2168      +/-   ##
==========================================
+ Coverage   82.48%   82.56%   +0.07%     
==========================================
  Files          91       91              
  Lines        8782     8815      +33     
==========================================
+ Hits         7244     7278      +34     
+ Misses       1538     1537       -1     

Files with missing lines	Coverage Δ
pydatalab/src/pydatalab/routes/v0_1/info.py	85.06% <100.00%> (+0.09%)	⬆️
pydatalab/src/pydatalab/config.py	85.56% <96.96%> (+3.46%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gpetretto]

LGTM. I just left a couple of minor comments.

[gpetretto]

Shouldn't it also give an error maybe. The most likely cause for seems a typo and it could be difficult to identify. Not sure how easy it is to implement.

[davidwaroquiers]

I would keep it like that for now, it's not so straightforward to do it at deployment time (at least for when there will be custom views).

[gpetretto]

In which case this would arrive to NAVIGATION_VIEWS.samples.routeName? And if there is such a case, what happens if the samples route is hidden from the top bar? Will the user end up there in any case?

[davidwaroquiers]

It's only if all the view ids are unknown to the frontend (or are considered unavailable for some reason - to be defined in the future), then it indeed goes to samples. Hiding a navigation tab does not remove the route, it remains accessible. So you would basically end up there if there is no "proper" navigation bar (which is different from having no defined navigation tab, these tabs could be "wrong" or "unavailable"). Unlikely case but at least there is a fallback.

[davidwaroquiers]

This should be ready for review @ml-evs.

My next step would be to introduce a "blocks table route" to be able to visualize blocks "independently" from their items (likely in read-only mode, to be discussed and possibly relaxed later). I would keep that "blocks table route" hidden by default in the navigation bar and if someone wants to show it he should use this new custom NAVIGATION config.

Any comment or feedback is welcome of course (note that the above screenshots are available on our previews if useful).

Note that I kept two comments from @gpetretto open in case you want to comment or have a request/solution for these.