Start9/start-os
2
0
Fork 0
mirror of https://github.com/Start9Labs/start-os.git synced 2026-04-04 22:39:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: small changes

Browse Source
This commit is contained in:
waterplea
2024-08-16 14:39:54 +04:00
parent 015131f198
commit 0abe08f243
4 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
web/projects/ui/src/app/routes/portal/routes/system/backups/modals/target.component.ts
View File

@@ -47,7 +47,6 @@ import { DataModel } from 'src/app/services/patch-db/data-model'
[type]="context.data.type" [type]="context.data.type"
[target]="target" [target]="target"
[serverId]="serverId" [serverId]="serverId"
]
/> />
<div [style.color]="'var(--tui-text-secondary'"> <div [style.color]="'var(--tui-text-secondary'">
{{ displayInfo.description }} {{ displayInfo.description }}
@@ -77,7 +76,7 @@ export class BackupsTargetModal {
private readonly dialogs = inject(TuiDialogService) private readonly dialogs = inject(TuiDialogService)
private readonly errorService = inject(ErrorService) private readonly errorService = inject(ErrorService)
private readonly api = inject(ApiService) private readonly api = inject(ApiService)
private readonly patch = inject(PatchDB<DataModel>) private readonly patch = inject<PatchDB<DataModel>>(PatchDB)
readonly context = readonly context =
inject<TuiDialogContext<BackupTarget, { type: BackupType }>>( inject<TuiDialogContext<BackupTarget, { type: BackupType }>>(

2
web/projects/ui/src/app/routes/portal/routes/system/metrics/metrics.service.ts
View File

@@ -25,7 +25,7 @@ export class MetricsService extends Observable<ServerMetrics> {
), ),
// @TODO Alex how to handle failure and reconnection here? Simple retry() will not work. Seems like we need a general solution for reconnecting websockets: patchDB, logs, metrics, progress, and any future. Reconnection should depend on server state, then we need to get a new guid, then reconnect. Similar to how patchDB websocket currently behaves on disconnect/reconnect. // @TODO Alex how to handle failure and reconnection here? Simple retry() will not work. Seems like we need a general solution for reconnecting websockets: patchDB, logs, metrics, progress, and any future. Reconnection should depend on server state, then we need to get a new guid, then reconnect. Similar to how patchDB websocket currently behaves on disconnect/reconnect.
retry(), retry(),
shareReplay(), shareReplay(1),
) )
constructor() { constructor() {

2
web/projects/ui/src/app/services/dep-error.service.ts
View File

@@ -38,7 +38,7 @@ export class DepErrorService {
), ),
), ),
distinctUntilChanged(deepEqual), distinctUntilChanged(deepEqual),
shareReplay({ bufferSize: 1, refCount: true }), shareReplay(1),
) )
constructor( constructor(

4
web/projects/ui/src/app/services/marketplace.service.ts
View File

@@ -76,7 +76,7 @@ export class MarketplaceService implements AbstractMarketplaceService {
map(({ selectedUrl: url, knownHosts: hosts }) => map(({ selectedUrl: url, knownHosts: hosts }) =>
toStoreIdentity(url, hosts[url]), toStoreIdentity(url, hosts[url]),
), ),
shareReplay({ bufferSize: 1, refCount: true }), shareReplay(1),
) )
private readonly marketplace$ = this.knownHosts$.pipe( private readonly marketplace$ = this.knownHosts$.pipe(
@@ -102,7 +102,7 @@ export class MarketplaceService implements AbstractMarketplaceService {
}, },
{}, {},
), ),
shareReplay({ bufferSize: 1, refCount: true }), shareReplay(1),
) )
private readonly filteredMarketplace$ = combineLatest([ private readonly filteredMarketplace$ = combineLatest([