hunk.code_window: Other instance operators that take a Scheduler as argument: `cache`, `combineLatest`, `concat`, `expand`, `merge`, `publishReplay`, `startWith`.
   Notice that both `cache` and `publishReplay` accept a Scheduler because they utilize a ReplaySubject. The constructor of a ReplaySubjects takes an optional Scheduler as the last argument because ReplaySubject may deal with time, which only makes sense in the context of a Scheduler. By default, a ReplaySubject uses the `queue` Scheduler to provide a clock.
  
hunk.labels: keep keep keep replace
hunk.after_edit: Notice that both `cache` and `publishReplay` accept a Scheduler because they utilize a ReplaySubject. The constructor of a ReplaySubjects takes an optional Scheduler as the last argument because ReplaySubject may deal with time, which only makes sense in the context of a Scheduler. By default, a ReplaySubject uses the `queueScheduler` Scheduler to provide a clock.
hunk.file_path: docs_app/content/guide/scheduler.md
hunk.type: replace
file: import { Injectable } from '@angular/core';
  import { LocationService } from 'app/shared/location.service';
  import { environment } from 'environments/environment';
  
  /**
   * Information about the deployment of this application.
   */
  @Injectable()
  export class Deployment {
    /**
     * The deployment mode set from the environment provided at build time;
     * or overridden by the `mode` query parameter: e.g. `...?mode=archive`
     */
    mode: string = this.location.search()['mode'] || environment.mode;
  
    constructor(private location: LocationService) {}
  };
  