Skip to content

build: bazel typescript targets should use tsickle for decorator processing #16906

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
merged 1 commit into from
Aug 29, 2019

Conversation

devversion
Copy link
Member

We want to enable tsickle for decorator processing. This was one of the
blockers for using the bazel packages in releases as unprocessed decorators
will end up referencing DOM specific globals (e.g. HTMLElement).

These references would then break server-side rendering for non CLI
projects. Read more about this angular/angular#30586

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 28, 2019
@devversion devversion force-pushed the build/workaround-for-tsickle branch 4 times, most recently from 6c5d4b4 to 01ec26d Compare August 28, 2019 22:25
…essing

We want to enable tsickle for decorator processing. This was one of the
blockers for using the bazel packages in releases as unprocessed decorators
will end up referencing DOM specific globals (e.g. `HTMLElement`).

These references would then break server-side rendering for non CLI
projects. Read more about this angular/angular#30586
@devversion devversion force-pushed the build/workaround-for-tsickle branch from 01ec26d to de2f8a9 Compare August 29, 2019 09:31
@devversion devversion marked this pull request as ready for review August 29, 2019 09:45
@devversion devversion requested review from jelbourn and a team as code owners August 29, 2019 09:45
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Aug 29, 2019
@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 29, 2019
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 57e31da into angular:master Aug 29, 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 29, 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 PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants