Skip to content

fix(router): workaround issues in closure compiler - #22870

Closed
vikerman wants to merge 1 commit into
angular:masterfrom
vikerman:router-closure
Closed

vikerman wants to merge 1 commit into
angular:masterfrom
vikerman:router-closure

Conversation

@vikerman

Copy link
Copy Markdown
Contributor

Spread operator in this particular place was throwing off closure(probably because it was thrown off by the of in the source).

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Current Angular code doesn't compile with certain closure compiler flag

What is the new behavior?

Works with closure

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Spread operator in this particular place was throwing off closure(probably because it was thrown off by the `of` in the source).
@vikerman
vikerman requested a review from IgorMinar March 19, 2018 23:05
@vikerman vikerman added the action: review The PR is still awaiting reviews from at least one requested reviewer label Mar 19, 2018
@mary-poppins

Copy link
Copy Markdown

You can preview fcb46cc at https://pr22870-fcb46cc.ngbuilds.io/.

@IgorMinar IgorMinar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

In #22573 I rewrote this to:

+  return of (...waitHead, ...waitTail).pipe(concatAll(), lastValue(), map(() => res));

will this still be problematic? In the meantime I suggest we don't merge this as is. If needed I can cherry-pick this to my PR.

@IgorMinar

Copy link
Copy Markdown
Contributor

I verified that this is no longer a problem with #22573. closing.

@IgorMinar IgorMinar closed this Mar 20, 2018
@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 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: review The PR is still awaiting reviews from at least one requested reviewer cla: yes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants