Mediator DTO

[GustavEikaas]

Mediator === Workspace core

My idea is that the app developer should in some cases get access to the mediator instance of the workspace.
This will allow the app developer to integrate their own components with the workspace, or solve weird edge cases.

The mediator consists of multiple services/states

{
  bookmarkService;
  dataService;
  selectionService;
  errorService;
  urlService;
  contextService; (custom state not to be confused with fusion context)
}

Exposing them directly seems unnecessary and tedious in terms of changes. I cant fathom any circumstance where an app developer would need to access the url service of fusion workspace. Because any changes would be overwritten.

Let's try to discuss cases that app developers possibly would need to solve and what functionality they would need to access..

I can imagine app developers might have to do the following;

• Set data
• Open a sidesheet
• Emit an error
• Set a bookmark/state
• Set context

My suggestion

type MediatorDTO<TData> = {
  setData: (newData: TData[]) => void;
  openSidesheet: (id: string, props: TProps) => void;
  setError: (error: WorkspaceFusionError) => void;
  setBookmark: (bookmark: FusionBookmark) => void;
  setContext: (filteredData: TData[], ...otherArgs???: unknown) => TContext;
}

[Gustav-Eikaas]

After discussion:
Looks good but add api property that exposes the raw thing. Better safe than sorry