Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-5489

Compass collection tabs should resolve their own metadata (handle its own loading state) when rendered

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • State Management, Tech debt
    • None
    • 8

    Description

      Now that Compass doesn't pre-fetch all the database and collection metadata before becoming interactive the fact that collection tab requires a ton of this metadata before it can be shown on the screen (all appRegistry events like select-namespace, open-namespace-in-new-tab, modify-view, etc., that can cause the tab to show need to fetch this information in advance) gets in the way quite a lot: there is no easy way to just open a new tab from the arbitrary part of Compass without making this part of Compass aware of all the collection metadata, even if it doesn't know anything about collection except for the namespace.

      We should consider moving the fetching logic to the compass-collection store and simplify the namespace selection events to the bare minimum: only namespace is absolutely required to be able to show collection tab

      Attachments

        Activity

          People

            Unassigned Unassigned
            sergey.petushkov@mongodb.com Sergey Petushkov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: