Skip to content

Conversation

@vicb
Copy link
Contributor

@vicb vicb commented Jul 27, 2018

supersedes #25092

(Rebased after recent changes to di.ts)

edit 7/29: added a second commit for misc refactoring + fix CI (had to revert a change I did on Friday as import * as viewEngine breaks tree shaking).

edit 7/30: As noted by @marclaval below, it was using Injector.NULL not import * as viewEngine that was breaking tree shaking. Updated the 2nd commit

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mhevery @marclaval
vcr.element returns a different instance each time and also !== vcr.injector.get(ElementRef)
is this the expected behavior ?

@mary-poppins
Copy link

You can preview a89b3b3 at https://pr25174-a89b3b3.ngbuilds.io/.

@vicb vicb added cla: yes action: review The PR is still awaiting reviews from at least one requested reviewer and removed cla: no labels Jul 27, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@vicb
Copy link
Contributor Author

vicb commented Jul 27, 2018

@marclaval @mhevery The original PR was green and good to go but I added a question before this can be merged. Feel free to add the "merge, ..." labels if this is not a problem. Thanks.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

nit: viewData ? viewData[INJECTOR] : null

Copy link
Contributor Author

Choose a reason for hiding this comment

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

nit: use element() when Start and End are back to back to conform to what the compiler generates.
(there is a PR pending for updating current specs)

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@vicb vicb added target: major This PR is targeted for the next major release comp: ivy labels Jul 29, 2018
@mary-poppins
Copy link

You can preview c763810 at https://pr25174-c763810.ngbuilds.io/.

@marclaval
Copy link
Contributor

@vicb about your question:
vcr.element returns a different instance each time and also !== vcr.injector.get(ElementRef)
is this the expected behavior ?

I don't know why but this is how it is done in the current engine: https://github.com/angular/angular/blob/master/packages/core/src/view/refs.ts#L137
I've kept the same behaviour.

@marclaval
Copy link
Contributor

@vicb: using Injector.NULL instead of new NullInjector() brings in a bunch of new tokens in the todo app bundle: https://circleci.com/gh/angular/angular/59905
It doesn't seem to be such a good idea.

@vicb
Copy link
Contributor Author

vicb commented Jul 30, 2018

using Injector.NUL instead of new NullInjector() ...

Thanks I was tracking this one. I will revert.

Wrt to a new instance of ElementRef, I'll discuss with Misko and we can update this PR accordingly so that it can be merged ASAP.

Thanks

@vicb vicb force-pushed the gh-25092 branch 2 times, most recently from 8091d1e to ea0dded Compare July 30, 2018 15:19
@mary-poppins
Copy link

You can preview 8091d1e at https://pr25174-8091d1e.ngbuilds.io/.

@mary-poppins
Copy link

You can preview ea0dded at https://pr25174-ea0dded.ngbuilds.io/.

@mary-poppins
Copy link

You can preview 8543f3d at https://pr25174-8543f3d.ngbuilds.io/.

@vicb vicb added cla: yes and removed cla: no labels Jul 30, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@vicb
Copy link
Contributor Author

vicb commented Jul 30, 2018

@mary-poppins
Copy link

You can preview 25f790b at https://pr25174-25f790b.ngbuilds.io/.

@marclaval
Copy link
Contributor

LGTM

@vicb vicb added action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jul 30, 2018
@IgorMinar IgorMinar requested a review from mhevery July 30, 2018 21:05
Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

just rubber-stamping to make CI happy - the original PR from Marc had all the approvals

@vicb vicb removed the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Jul 30, 2018
@IgorMinar IgorMinar removed the request for review from mhevery July 30, 2018 21:23
marclaval and others added 3 commits July 30, 2018 16:54
BREAKING CHANGE: ViewContainerRef.parentInjector is deprecated without replacement
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@vicb vicb added cla: yes and removed cla: no labels Jul 30, 2018
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@IgorMinar IgorMinar closed this in cd89eb8 Jul 31, 2018
IgorMinar pushed a commit that referenced this pull request Jul 31, 2018
@mary-poppins
Copy link

You can preview 1d86b37 at https://pr25174-1d86b37.ngbuilds.io/.

@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 13, 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 target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants