angular - How can I "monkey patch" an Observable for Zone.js? -


i'm creating angular 2 component, , angular's change detection isn't working me when using observable pattern. looks this:

    let getresult$ = this.http.get('/api/identity-settings');      let manager$ = getresult$         .map((response) => /* -- create manager object -- */);      let signinresponse$ = manager$         .flatmap(manager => manager.processsigninresponse());      this.readytologin$ = manager$.map(() => true).startwith(false);     this.isloggedin$ = signinresponse$.map(() => true).startwith(false);

then in template:

<h1>ready log in: {{readytologin$ | async}}</h1> <h1>logged in: {{isloggedin$ | async}}</h1>

since readytologin$ observable based on synchronous set of operations happen in response http.get() (which angular "monkey patches" ensure knows when needs detect changes), "ready log in" message switches true @ appropriate time.

however, since processsigninresponse() produces promise<>, subscribing result of flatmap occurring asynchronously http request's completion event. therefore, requires manual intervention notify component's zone needs check changes.

how can wrap signinresponse$ observable in way ngzone knows detect changes after subscriptions have been resolved?

update

brandon's answer worked until updated rc5, @ point things stopped working again. turns out the 3rd-party library using borked zone.js. once resolved, there no need use workaround @ all--the built-in monkey patching worked!

you can make new observeonzone operator can used "monkey patch" observable. like:

rx.observable.prototype.observeonzone = function (zone) {     return observable.create(observer => {         var onnext = (value) => zone.run(() => observer.next(value));         var onerror = (e) => zone.run(() => observer.error(e));         var oncomplete = () => zone.run(() => observer.complete());         return this.subscribe(onnext, onerror, oncomplete);     }); };

and use so:

this.isloggedin$ = signinresponse$.map(() => true).startwith(false).observeonzone(zone);

-

Popular posts from this blog

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more