[UI] Registry enhancement about meshery

[Yashsharma1911]

@dottharun I created this task to track the issue, I have added the you shared with me, please add more as you identify.

[github-actions]

This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests.

---

        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄

[leecalcote]

End-to-end tests needed for importing and exporting models. @dottharun @humblenginr #11555 (comment)

[dottharun]

More Issues: @Yashsharma1911

• Make the meshmodel details component respect the level of navigation of
  the current tree.
  • Show aggregate count of the number of components in all of the
    versioned models - for the top-level model.
• Fix component and relationship count bug - currently both shows zero.
• Fix initial load of models tab and with page-size large enough to always
  cover the first page.
• Add empty state when numbered nodes in Tree like components and
  relationships becomes zero - currently this just shows zero in brackets
  (0).
• Convert all tabs to use IntersectionObserver.
  • Currently only Models and Registrants tab uses this - and
    Components tab uses scroll based fetching.
• Add query param for the meshmodel/models,
  meshmodels/components, meshmodels/relationships,
  meshmodels/registrants endpoints.
  • Like a "duplication-data=true" to get information about
    duplication of the entities and use those in the UI to filter and
    annotate duplicate entities.
• Add Id based endpoints for GET requests for all Registry endpoints to allow for easy selection of entities
  • currently its based on name and version in combination
  • maybe related - meshery/meshkit#538

[Yashsharma1911]

Thankyou @dottharun I have few suggestion for you to look into

• Fix initial load of models tab and with page-size large enough to always cover the first page.

Isn't this one already fixed with having observer implemented?

• Add empty state when numbered nodes in Tree like components and relationships becomes zero - currently this just shows zero in brackets (0).

How will you add Empty state? if number is zero they should be disabled right? I wonder if empty state in tree is unnecessary logic wdyt?

[dottharun]

• Fix initial load of models tab and with page-size large enough to always cover the first page.

Isn't this one already fixed with having observer implemented?

• It still has some buggy behavior if we navigate to the page
  from the registry (by clicking). The fetching event is stuck at the
  first page. This should probably be fixed by increasing the page_size to cover
  the first page.

How will you add Empty state? if number is zero they should be disabled right? I wonder if empty state in tree is unnecessary logic wdyt?

• Yes, this is a low priority enrichment item.

[amitamrutiya]

Hey @sudhanshutech, I would like to work on this.

[amitamrutiya]

Hey @Yashsharma1911 @sudhanshutech, I need some help from you guys. Before working on this issue, I want to confirm that I understand some problems correctly.

Fix route based details on MeshModelsDetails Component

• Screencast from 2024-08-19 21-42-10.webm

Router should work with infiniteScroll - currently it breaks after first page

• Screencast.from.2024-08-19.21-49-58.webm

• I need to fix the above issues mentioned in the videos, right?

Duplication of data from endpoint should be removed

• Make changes to the backend endpoint written in Go and remove data duplication.

Am I understand correctly ?