Skip to content

fix(router): ensure history.state is set in eager update mode - #30154

Closed
jasonaden wants to merge 1 commit into
angular:masterfrom
jasonaden:FW-898_pass_state_update
Closed

jasonaden wants to merge 1 commit into
angular:masterfrom
jasonaden:FW-898_pass_state_update

Conversation

@jasonaden

Copy link
Copy Markdown
Contributor

Without this change, history.state isn't being set when updating the browser URL in eager update mode.

Without this change, `history.state` isn't being set when updating the browser URL in `eager` update mode.
@jasonaden
jasonaden requested a review from a team April 26, 2019 18:41
@jasonaden jasonaden added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release area: router type: bug/fix labels Apr 26, 2019
@ngbot ngbot Bot added this to the needsTriage milestone Apr 26, 2019
@jasonaden

Copy link
Copy Markdown
Contributor Author

Presubmit

@kara

kara commented May 6, 2019

Copy link
Copy Markdown
Contributor

@jasonaden Can you look at the TAP failures here?

@kara kara added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label May 6, 2019
@jasonaden jasonaden removed the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label May 6, 2019
@kara kara closed this in b40f6f3 May 6, 2019
kara pushed a commit that referenced this pull request May 6, 2019
…0154)

Without this change, `history.state` isn't being set when updating the browser URL in `eager` update mode.

PR Close #30154
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…gular#30154)

Without this change, `history.state` isn't being set when updating the browser URL in `eager` update mode.

PR Close angular#30154
@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 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 area: router cla: yes target: patch This PR is targeted for the next patch release type: bug/fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants