Skip to content

build: remove devmode tsickle decorator processing workaround #19405

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

Merged

Conversation

devversion
Copy link
Member

@devversion devversion commented May 20, 2020

In the past, we added a workaround for angular/angular#30586,
so that tsickle actually runs on the devmode output. We can remove this since there
is a more simpler workaround until View Engine is completely gone. Ivy is supposed
to fix this unless the output format is modified to preserve TS decorator calls.

If that would be the case (it's not at time of writing), then we can
still use the global mocking (which is not that unreasonable), or wire
up build optimizer (which would be quite complicated in Bazel).

This is a preparation change for angular/angular#37221, but generally is useful as it simplifies the workaround.

@devversion devversion added merge safe target: major This PR is targeted for the next major release labels May 20, 2020
@devversion devversion requested review from jelbourn and a team as code owners May 20, 2020 17:30
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 20, 2020
@devversion devversion force-pushed the build/remove-tsickle-decorator-processing branch from af1ec39 to 3a20a25 Compare May 20, 2020 17:33
In the past, we added a workaround for angular/angular#30586,
so that tsickle actually runs on the devmode output. We can remove this since there
is a more simpler workaround until View Engine is completely gone. Ivy is supposed
to fix this unless the output format is modified to preserve TS decorator calls.

If that would be the case (it's not at time of writing), then we can
still use the global mocking (which is not that unreasonable), or wire
up build optimizer (which would be quite complicated in Bazel).
@devversion devversion force-pushed the build/remove-tsickle-decorator-processing branch from 3a20a25 to 94de333 Compare May 20, 2020 17:44
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn merged commit 8127185 into angular:master May 21, 2020
@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 Jun 21, 2020
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 PR author has agreed to Google's Contributor License Agreement target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants