Skip to content

build: validate bazel rollup globals #17173

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 3 commits into from
Oct 1, 2019

Conversation

devversion
Copy link
Member

@devversion devversion commented Sep 23, 2019

  • See individual commits.

Note: to reduce too much changes to the gulp build system yet, the rollup globals tslint rule will remain for now.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 23, 2019
@devversion devversion marked this pull request as ready for review September 23, 2019 10:07
@devversion devversion 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 Sep 23, 2019
@devversion devversion force-pushed the build/rollup-globals-validation branch 4 times, most recently from c4ed87d to 1cd823b Compare September 23, 2019 12:22
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 added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 23, 2019
@devversion devversion force-pushed the build/rollup-globals-validation branch 2 times, most recently from 15a8f12 to 0ffe8f0 Compare September 24, 2019 08:17
@devversion
Copy link
Member Author

Rebased since the form-field harness got merged and otherwise the rollup globals check would fail.

@devversion devversion force-pushed the build/rollup-globals-validation branch from 0ffe8f0 to 461ceb9 Compare September 24, 2019 12:13
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, just one nit

@devversion devversion added this to the 9.0.0 milestone Oct 1, 2019
We can't import individual files through the module name because:

* We don't have these listed in the rollup globals
* These imports will break in the Angular package (due to limitation in APF).
Apparently the rollup globals tslint rule did not check all files. Resuling
in a few cases where the rollup globals were missing.
We currently need to also maintain a list
of rollup globals for bazel. Since these globals
are impacting the release output we need to check
these somehow in order to be sure that we do not
accidentally bundle other entry-points into an
entry-point.
@devversion devversion force-pushed the build/rollup-globals-validation branch from 461ceb9 to e19092e Compare October 1, 2019 12:10
@mmalerba mmalerba added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful and removed P2 The issue is important to a large percentage of users, with a workaround labels Oct 1, 2019
@mmalerba mmalerba merged commit bf304e9 into angular:master Oct 1, 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 Nov 1, 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 P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants