Deliver Observable read values as microtasks instead of after a timer

Aberta
  • Algo errado?
#3,832 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
74/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
angular, typescript
Domínio
api

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
7.8k
Forks
2.2k
Merge médio
2d 12h
PRs com merge (30d)
24

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de angular/angularfire

Todas as issues de angular/angularfire

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.