Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ivy): <ng-container> fixes #25617

Conversation

pkozlowski-opensource
Copy link
Member

This PR contains fixes for 2 issues discovered when running TestBed spec on the existing tests from the common package.

In both cases the issue boiled down to taking new node type into account when doing checks.

@pkozlowski-opensource pkozlowski-opensource added action: review The PR is still awaiting reviews from at least one requested reviewer target: major This PR is targeted for the next major release comp: ivy labels Aug 22, 2018
@mary-poppins
Copy link

You can preview 70866ec at https://pr25617-70866ec.ngbuilds.io/.

}

function typeName(type: TNodeType): string {
if (type == TNodeType.Projection) return 'Projection';
if (type == TNodeType.Container) return 'Container';
if (type == TNodeType.View) return 'View';
if (type == TNodeType.Element) return 'Element';
if (type == TNodeType.ElementContainer) return 'ElementContainer';
return '<unknown>';
Copy link
Contributor

Choose a reason for hiding this comment

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

Would this be more performant? j/w

// Move this object outside so it only gets created once
const nodeTypeName = {
  TNodeType.Projection: 'Projection',
  TNodeType.Container: 'Container',
  TNodeType.View: 'View',
  TNodeType.Element: 'Element',
  TNodeType.ElementContainer: 'ElementContainer',
};

return nodeTypeName[type] || '<unknown>';

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think that performance is consideration here since this is just assert code not present in production bundles.

elementContainerEnd();
}
if (rf & RenderFlags.Update) {
const tplRef = load(1);
Copy link
Contributor

Choose a reason for hiding this comment

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

reference here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Right, good catch, thnx!

@mary-poppins
Copy link

You can preview 277a8ba at https://pr25617-277a8ba.ngbuilds.io/.

Copy link
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

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

LGTM

@kara
Copy link
Contributor

kara commented Aug 23, 2018

presubmit

@kara kara added type: bug/fix and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Aug 23, 2018
@pkozlowski-opensource pkozlowski-opensource added the action: merge The PR is ready for merge by the caretaker label Aug 24, 2018
@matsko matsko closed this in b00038c Aug 24, 2018
FrederikSchlemmer pushed a commit to FrederikSchlemmer/angular that referenced this pull request Jan 3, 2019
FrederikSchlemmer pushed a commit to FrederikSchlemmer/angular that referenced this pull request Jan 3, 2019
@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 type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants