[COMPASS-5130] Remove compass-instance-model and move instance fetching to compass-home Created: 01/Oct/21  Updated: 20/Oct/21  Resolved: 20/Oct/21

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: None
Fix Version/s: No version

Type: Task Priority: Major - P3
Reporter: Rhys Howell Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on COMPASS-5133 Move compass-home to typescript Closed
is depended on by COMPASS-5131 Make instance detail fetching not wai... Closed
Epic Link: COMPASS-4764
Story Points: 3
Documentation Changes: Not Needed
Sprint: Iteration Minsk, Iteration Novokuybyshevsk

 Description   

Currently we're fetching compass' instance when the global `refresh-data` message is emitted in the app registry and when the data service connects `data-service-connected`. This is handled by compass-app-stores which has an instance of mongodb-instance-model. This ticket involves moving the handling of those events to `compass-home` and keeping the instance in the state of the component there (where it can be, in later tickets, passed through props to components). We should remove mongodb-instance-model then and keep it as a plain object.

It does look like there are some places that rely on `global.hadronApp.instance` being available, we should continue letting it be so unless we want to address it in this ticket.

Maurizio's gist of moving instance fetching to ts and has a few cleanups also: https://gist.github.com/mcasimir/7f089a2e66018cf12c4cc1e516b08526



 Comments   
Comment by Sergey Petushkov [ 20/Oct/21 ]

Closed due to restructuring the work around changing the global overlay behaviour when fetching data. See this Miro board for the reference

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