Category UI state

[codemonkey800]

Sets up the UI state necessary for storing category and category hierarchy data from the backend, and reading that data for filtering and rendering.

The TypeScript interfaces for the category data were taken from the napari-demo plugin:

https://api.staging.napari-hub.org/plugins/napari-demo

  "category": {
    "Supported data": [
      "2D", 
      "3D"
    ], 
    "Workflow step": [
      "Image Segmentation", 
      "Image annotation"
    ]
  }, 
  "category_hierarchy": {
    "Supported data": [
      [
        "2D"
      ], 
      [
        "3D"
      ]
    ], 
    "Workflow step": [
      [
        "Image Segmentation", 
        "Manual segmentation"
      ], 
      [
        "Image annotation", 
        "Dense image annotation", 
        "Manual segmentation"
      ], 
      [
        "Image Segmentation", 
        "Semi-automatic segmentation"
      ]
    ]
  }, 

[shortcut-integration]

This pull request has been linked to Shortcut Story #172043: Category UI State.

[klai95]

Very nice test case!

[klai95]

Would the triple for loop become a performance bottleneck? I am not sure if there is a way to get around it, but just wanted to get some clarity on this!

[codemonkey800]

Great feedback! 🤩

It could be if the amount of categories and category keys increase a lot. That would be basically O(NMK) 🤣 I can't think of a better way at the moment since:

1. We need to iterate the entire list of N plugins.
2. We need to iterate up to M categories.
3. We need to iterate over all K keys so we can populate the form state.

There's no way around this because we need to figure out the entire set of keys possible, and the only way to do that is by looking at every key for every category for every plugin.

I'm not too worried also because our existing category datasets are small, and we are eventually planning to move the search to the backend so that user's don't have to compute this on their devices

[klai95]

Nicely done!