Deliver Observable read values as microtasks instead of after a timer

Ouverte
  • Quelque chose ne va pas ?
#3,832 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
74/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
angular, typescript
Domaine
api

Piste de recherche

Start with src/zones.ts:82 and the ɵzoneWrap path described in the issue; check how schedulers.insideAngular is used by the Observable wrappers. Add or update tests for the timing behavior, including a wrapped Subject and the affected compat streams. Done means values reach subscribers in a microtask after the current task, not synchronously or after a timer.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

comp: compat comp: ssr comp: zones type: feature version: current (v17+)
Version info

Angular: 22.2

Firebase: 12.19.0

AngularFire: 22.0.0-rc.0, and main

Description

Every Observable-returning read waits one timer turn before its subscriber sees a value:

  • ɵzoneWrap pipes those reads (collectionData, docData, authState, user, objectVal, listVal, fromTask, the Remote Config get*Changes streams, 34 wrappers across the modular modules including Firestore Lite) through observeOn(schedulers.insideAngular).
  • That scheduler is built over rxjs asyncScheduler (src/zones.ts:82), which defers with setInterval, so each value reaches the subscriber one macrotask after Firebase handed it over.
  • For Firestore that is a second timer: the SDK already hands each snapshot to its callback inside a setTimeout(0).
  • The scheduler came in with #2243 (merged 2020), and the comment that PR added requires that emissions are never synchronous. rxjs's AsapScheduler, which defers with Promise.resolve().then, meets that requirement and delivers at the next microtask checkpoint, before any timer.

The compat layer is affected:

  • The AngularFireAuth streams authState, user and credential deliver through the same scheduler instance and inherit whichever timing it has.
  • AngularFireFunctions and AngularFireMessaging use it only to hand over the SDK instance before their work starts, so their results are not delivered through it.
  • Compat Database and Firestore deliver through schedulers.outsideAngular and are not part of this.
How to reproduce these conditions

On a fresh Angular 22.2 app with @angular/fire@next, wrap a Subject with the real ɵzoneWrap, subscribe, and at the moment the source emits register a setTimeout(0) and a queueMicrotask:

  • When the subscriber runs, the timer has already fired, in a zone.js app and a zoneless one, in Chrome and Firefox.
  • The real collectionData against the Firestore emulator and the compat authState against the Auth emulator behave the same way in Chrome.
  • With an AsapScheduler in place of asyncScheduler, the microtask has fired and the timer has not, in every one of those runs.
Expected behavior

A value Firebase produced is handed to the subscriber as soon as the current task finishes, without an extra timer turn.

Actual behavior

Every value waits for a setInterval callback.

Langage dominant
TypeScript
Étoiles
7.8k
Forks
2.2k
Merge moyen
2 j 12 h
PR mergées (30 j)
24

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de angular/angularfire

Toutes les issues de angular/angularfire

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.