mgechev / mgechev/eap-feedback
Profiler Change Detection source is always `fakeTopEventTask` when `ngZoneEventCoalescing` is set to true
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 10
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
When I set `ngZoneEventCoalescing` to true in my `main.ts` and running the profiler, the Change Detection event source is always set to `fakeTopEventTask`.
Now - It sounds reasonable, I just think that the source inside the profiler is one of the most efficient ways to track CD issues.
Any chance we do something to make it more informative even when Zone coalescing is on?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the profiler behavior from the Angular application entry point in main.ts with ngZoneEventCoalescing enabled, then trace how the profiler assigns the Change Detection event source. Done means the source is informative rather than always fakeTopEventTask when coalescing is enabled; no test or implementation file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100