forked from hazza/dspace-angular

- Also fixed an issue where the collection switcher could accidentally show the old collection name instead of the new one - Also updated the WorkspaceItemPageResolver & WorkflowItemPageResolver to embed the collection to use fewer requests
36 lines
1.5 KiB
TypeScript
36 lines
1.5 KiB
TypeScript
import { Injectable } from '@angular/core';
|
|
import { ActivatedRouteSnapshot, Resolve, RouterStateSnapshot } from '@angular/router';
|
|
import { Observable } from 'rxjs';
|
|
import { RemoteData } from '../core/data/remote-data';
|
|
import { followLink } from '../shared/utils/follow-link-config.model';
|
|
import { WorkflowItemDataService } from '../core/submission/workflowitem-data.service';
|
|
import { WorkflowItem } from '../core/submission/models/workflowitem.model';
|
|
import { getFirstCompletedRemoteData } from '../core/shared/operators';
|
|
|
|
/**
|
|
* This class represents a resolver that requests a specific workflow item before the route is activated
|
|
*/
|
|
@Injectable()
|
|
export class WorkflowItemPageResolver implements Resolve<RemoteData<WorkflowItem>> {
|
|
constructor(private workflowItemService: WorkflowItemDataService) {
|
|
}
|
|
|
|
/**
|
|
* Method for resolving a workflow item based on the parameters in the current route
|
|
* @param {ActivatedRouteSnapshot} route The current ActivatedRouteSnapshot
|
|
* @param {RouterStateSnapshot} state The current RouterStateSnapshot
|
|
* @returns Observable<<RemoteData<Item>> Emits the found workflow item based on the parameters in the current route,
|
|
* or an error if something went wrong
|
|
*/
|
|
resolve(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<RemoteData<WorkflowItem>> {
|
|
return this.workflowItemService.findById(route.params.id,
|
|
true,
|
|
false,
|
|
followLink('item'),
|
|
followLink('collection'),
|
|
).pipe(
|
|
getFirstCompletedRemoteData(),
|
|
);
|
|
}
|
|
}
|