Skip to content

fix(async): handle synchronous initial value in async pipe - #5996

Closed
robwormald wants to merge 1 commit into
angular:masterfrom
robwormald:fix/asyncpipe
Closed

robwormald wants to merge 1 commit into
angular:masterfrom
robwormald:fix/asyncpipe

Conversation

@robwormald

Copy link
Copy Markdown
Contributor

closes #5992 - values delivered sync via the async pipe would cause change detection errors in dev mode.

@robwormald robwormald added the action: review The PR is still awaiting reviews from at least one requested reviewer label Dec 18, 2015
@robwormald

Copy link
Copy Markdown
Contributor Author

cc @vsavkin

@mary-poppins

Copy link
Copy Markdown

Merging PR #5996 on behalf of @alexeagle to branch presubmit-alexeagle-pr-5996.

@mary-poppins

Copy link
Copy Markdown

Merging PR #5996 on behalf of @alexeagle to branch presubmit-alexeagle-pr-5996.

@0x-r4bbit

Copy link
Copy Markdown
Contributor

Yay! Thank you @robwormald

/cc @cburgdorf

@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Async Pipe should handle default Scheduled Observable values appropriately

7 participants