Skip to content

Conversation

@devversion
Copy link
Member

a6cdcfc added the share() operator to the isHandset$ observable. This accidentally
broke the initial rendering of the navigation as the view subscribes to the observable
(through async pipe) after the initial value has been emitted. Meaning that isHandset$ | async
expression always evaluates to null until the breakpoint changes.

…nitial render

angular@a6cdcfc added the `share()` operator to the
`isHandset$` observable. This accidentally broke the initial rendering of the navigation as the view subscribes
to the observable (through `async` pipe) after the initial value has been emitted. Meaning that `isHandset$ | async`
expression always evaluates to `null` until the breakpoint changes.
@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Aug 15, 2019
@devversion devversion requested a review from jelbourn as a code owner August 15, 2019 13:25
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 15, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 15, 2019
@jelbourn jelbourn merged commit 3205b31 into angular:master Aug 15, 2019
andrewseguin pushed a commit that referenced this pull request Aug 26, 2019
…nitial render (#16788)

a6cdcfc added the `share()` operator to the
`isHandset$` observable. This accidentally broke the initial rendering of the navigation as the view subscribes
to the observable (through `async` pipe) after the initial value has been emitted. Meaning that `isHandset$ | async`
expression always evaluates to `null` until the breakpoint changes.

(cherry picked from commit 3205b31)
@angular-automatic-lock-bot
Copy link

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 15, 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 PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants