[COMPASS-5489] Compass collection tabs should resolve their own metadata (handle its own loading state) when rendered Created: 04/Feb/22  Updated: 22/Jun/23

Status: Open
Project: Compass
Component/s: State Management, Tech debt
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sergey Petushkov Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Story Points: 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


Generated at Wed Feb 07 22:39:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.