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

feat(bazel): allow passing a custom bazel compiler host to ngc compile #31341

Closed
wants to merge 1 commit into from

Conversation

ayazhafiz
Copy link
Member

Enable users to pass a custom Bazel CompilerHost to use for an Angular
compilation. This supports users who must override the TypeScript
compiler host.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Users cannot pass a specialized compiler host to ngc_wrapped#compile

Issue Number: N/A

What is the new behavior?

Users can pass a specialized compiler host to ngc_wrapped#compile

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Enable users to pass a custom Bazel CompilerHost to use for an Angular
compilation. This supports users who must override the TypeScript
compiler host.
@ayazhafiz ayazhafiz added feature Issue that requests a new feature target: major This PR is targeted for the next major release area: bazel Issues related to the published `@angular/bazel` build rules labels Jun 28, 2019
@ayazhafiz ayazhafiz requested a review from a team as a code owner June 28, 2019 15:40
@ayazhafiz ayazhafiz self-assigned this Jun 28, 2019
@ngbot ngbot bot added this to the needsTriage milestone Jun 28, 2019
Copy link
Contributor

@kyliau kyliau left a comment

Choose a reason for hiding this comment

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

This is for the Angular indexer inside Google. The indexer does not have access to file system, and must perform fs operations through a proxy. Allowing the compile function to accept a bazelHost provides a way to talk to the proxy.

@ayazhafiz ayazhafiz removed the request for review from alexeagle June 28, 2019 18:27
@ayazhafiz ayazhafiz added the action: merge The PR is ready for merge by the caretaker label Jun 28, 2019
@alxhub alxhub closed this in a29dc96 Jun 28, 2019
ayazhafiz added a commit to ayazhafiz/angular that referenced this pull request Jul 2, 2019
Updates the decision made in angular#31341; this is for the Angular indexer
inside Google. The indexer currently passes (and ngc-wrapped#compile
accepts) a bazel host to use, but because many methods are overwritten
specially for Angular compilation a better approach is to pass an old
bazel compiler host and siphon methods needed off of it before creating
a new host. This enables that.
alxhub pushed a commit that referenced this pull request Jul 2, 2019
Updates the decision made in #31341; this is for the Angular indexer
inside Google. The indexer currently passes (and ngc-wrapped#compile
accepts) a bazel host to use, but because many methods are overwritten
specially for Angular compilation a better approach is to pass an old
bazel compiler host and siphon methods needed off of it before creating
a new host. This enables that.

PR Close #31381
@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 15, 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 area: bazel Issues related to the published `@angular/bazel` build rules cla: yes feature Issue that requests a new feature target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants