Usage of ngZone.run for new async apis that zone.js hasn't pathced

Description

Is this demo correct? how ngZone knows when to update the view as zone.js hasn’t patch someNewAsyncAPI

export class AppComponent implements OnInit {
  constructor(private ngZone: NgZone) {}
  ngOnInit() {
    // New async API is not handled by Zone, so you need to
    // use ngZone.run() to make the asynchronous operation in the Angular zone
    // and trigger change detection automatically.
    this.ngZone.run(() => {
      someNewAsyncAPI(() => {
        // update the data of the component
      });
    });
  }
}

What is the affected URL?

https://angular.io/guide/zone#ngzone-run-and-runoutsideofangular

Please provide the steps to reproduce the issue

No response

Please provide the expected behavior vs the actual behavior you encountered

I think the demo code should be updated as below:

export class AppComponent implements OnInit {
  constructor(private ngZone: NgZone) {}
  ngOnInit() {
    // New async API is not handled by Zone, so you need to
    // use ngZone.run() to make the asynchronous operation in the Angular zone
    // and trigger change detection automatically.
-    this.ngZone.run(() => {
      someNewAsyncAPI(() => {
+        this.ngZone.run(() => {
        // update the data of the component
+        });
      });
-    });
  }
}

Please provide a screenshot if possible

No response

Please provide the exception or error you saw

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version.

No response

[JoostK]

Indeed!

[JoostK]

I believe you are correct; NgZone.run needs to be within the async closure, not around its registration.