Skip to content

fix: ensure components work with ES2015 in jit mode - #12759

Merged
jelbourn merged 1 commit into
angular:masterfrom
devversion:fix/table-rendering-es2015
Aug 21, 2018
Merged

fix: ensure components work with ES2015 in jit mode#12759
jelbourn merged 1 commit into
angular:masterfrom
devversion:fix/table-rendering-es2015

Conversation

@devversion

@devversiondevversion commented Aug 20, 2018

Copy link
Copy Markdown
Member

Fixes that some components does not render properly when used inside of a ES2015 JIT application. This is due to an ongoing Angular issue which has been caused due to a brittle Regex check introduced here that should be replaced with a more clean approach for identifying classes that inherit metadata from another class.

See the more detailed issue here: #12760

Fixes#9329.

@devversiondevversion added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Aug 20, 2018
@googlebotgooglebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 20, 2018

@jelbournjelbourn 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.

LGTM

@jelbournjelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 20, 2018
Fixes that some components does not render properly when used inside of a ES2015 JIT application. This is due to an ongoing Angular issue which has been caused due to a brittle Regex check [introduced here](angular/angular#22356 (comment)) that should be replaced with a more clean approach for identifying classes that inherit metadata from another class.
* angular/angular#22642
* angular/tsickle#760
See the more detailed issue here: angular#12760Fixesangular#9329.
@devversion
devversionforce-pushed the fix/table-rendering-es2015 branch from 597c324 to 008ccc1CompareAugust 20, 2018 20:24
@devversiondevversion changed the title fix(table): not rendering properly in es2015 appsfix: ensure components work with ES2015 in jit mode.Aug 20, 2018
@devversiondevversion changed the title fix: ensure components work with ES2015 in jit mode.fix: ensure components work with ES2015 in jit modeAug 20, 2018
@devversiondevversion removed pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 20, 2018
@devversion

Copy link
Copy Markdown
MemberAuthor

@jelbourn I've updated the PR to include the other workarounds as well. Please have another look.

@jelbournjelbourn 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.

LGTM

@jelbournjelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 20, 2018
@jelbourn
jelbourn merged commit 2adced1 into angular:masterAug 21, 2018
@devversion
devversion deleted the fix/table-rendering-es2015 branch August 21, 2018 18:34
jelbourn pushed a commit that referenced this pull request Aug 29, 2018
Fixes that some components does not render properly when used inside of a ES2015 JIT application. This is due to an ongoing Angular issue which has been caused due to a brittle Regex check [introduced here](angular/angular#22356 (comment)) that should be replaced with a more clean approach for identifying classes that inherit metadata from another class.
* angular/angular#22642
* angular/tsickle#760
See the more detailed issue here: #12760Fixes#9329.
@devversiondevversion mentioned this pull request Sep 6, 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-botangular-automatic-lock-botBot locked and limited conversation to collaborators Sep 9, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: mergeThe PR is ready for merge by the caretakercla: yesPR author has agreed to Google's Contributor License AgreementP2The issue is important to a large percentage of users, with a workaroundtarget: patchThis PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Table] Does not work when targetting ES6

3 participants

@devversion@jelbourn@googlebot