angular-docs-cn/aio/src/app/navigation/navigation.service.ts

93 lines
3.5 KiB
TypeScript
Raw Normal View History

2017-03-01 11:55:46 +00:00
import { Injectable } from '@angular/core';
import { Http } from '@angular/http';
import { Observable } from 'rxjs/Observable';
import { AsyncSubject } from 'rxjs/AsyncSubject';
2017-03-01 11:55:46 +00:00
import { combineLatest } from 'rxjs/observable/combineLatest';
import 'rxjs/add/operator/publishReplay';
import 'rxjs/add/operator/publishLast';
2017-03-01 11:55:46 +00:00
import { Logger } from 'app/shared/logger.service';
import { LocationService } from 'app/shared/location.service';
import { NavigationNode } from './navigation-node';
export { NavigationNode } from './navigation-node';
2017-03-01 11:55:46 +00:00
export interface NavigationViews {
[name: string]: NavigationNode[];
2017-03-01 11:55:46 +00:00
}
2017-03-06 14:15:57 +00:00
const navigationPath = 'content/navigation.json';
2017-03-01 11:55:46 +00:00
@Injectable()
export class NavigationService {
/**
* An observable collection of NavigationNode trees, which can be used to render navigational menus
*/
navigationViews = this.fetchNavigationViews();
/**
* An observable array of nodes that indicate which nodes in the `navigationViews` match the current URL location
*/
selectedNodes = this.getSelectedNodes();
2017-03-01 11:55:46 +00:00
constructor(private http: Http, private location: LocationService, private logger: Logger) { }
2017-03-01 11:55:46 +00:00
/**
* Get an observable that fetches the `NavigationViews` from the server.
* We create an observable by calling `http.get` but then publish it to share the result
* among multiple subscribers, without triggering new requests.
* We use `publishLast` because once the http request is complete the request observable completes.
* If you use `publish` here then the completed request observable will cause the subscribed observables to complete too.
* We `connect` to the published observable to trigger the request immediately.
* We could use `.refCount` here but then if the subscribers went from 1 -> 0 -> 1 then you would get
* another request to the server.
* We are not storing the subscription from connecting as we do not expect this service to be destroyed.
*/
private fetchNavigationViews(): Observable<NavigationViews> {
2017-03-06 14:17:49 +00:00
const navigationViews = this.http.get(navigationPath)
.map(res => res.json() as NavigationViews)
.publishLast();
2017-03-06 14:17:49 +00:00
navigationViews.connect();
return navigationViews;
2017-03-01 11:55:46 +00:00
}
/**
* Get an observable that will list the nodes that are currently selected
* We use `publishReplay(1)` because otherwise subscribers will have to wait until the next
* URL change before they receive an emission.
* See above for discussion of using `connect`.
*/
private getSelectedNodes() {
const selectedNodes = combineLatest(
this.navigationViews.map(this.computeUrlToNodesMap),
this.location.currentUrl,
(navMap, url) => navMap[url] || [])
.publishReplay(1);
selectedNodes.connect();
return selectedNodes;
2017-03-01 11:55:46 +00:00
}
/**
* Compute a mapping from URL to an array of nodes, where the first node in the array
* is the one that matches the URL and the rest are the ancestors of that node.
*
* @param navigation A collection of navigation nodes that are to be mapped
*/
private computeUrlToNodesMap(navigation: NavigationViews) {
const navMap = {};
Object.keys(navigation).forEach(key => navigation[key].forEach(node => walkNodes(node)));
2017-03-01 11:55:46 +00:00
return navMap;
function walkNodes(node: NavigationNode, ancestors: NavigationNode[] = []) {
const nodes = [node, ...ancestors];
if (node.url) {
// only map to this node if it has a url associated with it
navMap[node.url] = nodes;
2017-03-01 11:55:46 +00:00
}
if (node.children) {
node.children.forEach(child => walkNodes(child, nodes));
2017-03-01 11:55:46 +00:00
}
}
}
}