Skip to content

build(bazel): remove workaround no longer needed for module names for ngfactory & ngsummary files #25604

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

Conversation

gregmagolan
Copy link
Contributor

Resolves angular/angular-cli#11835.

The underlying issue in the compiler that required this workaround to give ngfactory & ngsummary files proper AMD names has been resolved so it is no longer needed.

@gregmagolan gregmagolan requested a review from alexeagle August 21, 2018 21:11
@gregmagolan gregmagolan added the target: patch This PR is targeted for the next patch release label Aug 21, 2018
@mary-poppins
Copy link

You can preview 81998de at https://pr25604-81998de.ngbuilds.io/.

@gregmagolan gregmagolan requested a review from alxhub August 21, 2018 22:48
@gregmagolan
Copy link
Contributor Author

For reference: the workaround was added in #25335

Copy link
Member

@alxhub alxhub left a comment

Choose a reason for hiding this comment

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

This change looks good to me!

The only thing I would ask is that you please add a commit description which details exactly what the workaround was for, and what changed which caused it to no longer be necessary. I'd be happy to approve this PR with that minor change :)

… ngfactory & ngsummary files

Workaround was added in #25335. It was necessary for .ngfactory & .ngsummary files to have proper AMD module names starting with @angular when building angular downstream from source using Bazel. The underlying issue has been resolved in the compiler and these files now get proper AMD module names without the need for this workaround. The workaround had an unexpected consequence angular/angular-cli#11835 which is fixed by its removal.
@gregmagolan gregmagolan force-pushed the revert-amd-module-name-for-ngfactory branch from 81998de to c4b36a9 Compare August 21, 2018 23:20
@mary-poppins
Copy link

You can preview c4b36a9 at https://pr25604-c4b36a9.ngbuilds.io/.

@alexeagle alexeagle added the action: merge The PR is ready for merge by the caretaker label Aug 22, 2018
matsko pushed a commit that referenced this pull request Aug 23, 2018
… ngfactory & ngsummary files (#25604)

Workaround was added in #25335. It was necessary for .ngfactory & .ngsummary files to have proper AMD module names starting with @angular when building angular downstream from source using Bazel. The underlying issue has been resolved in the compiler and these files now get proper AMD module names without the need for this workaround. The workaround had an unexpected consequence angular/angular-cli#11835 which is fixed by its removal.

PR Close #25604
@matsko matsko closed this in 22d58fc Aug 23, 2018
@StephenFluin
Copy link
Contributor

@alexeagle I think you said we also need another test for this

FrederikSchlemmer pushed a commit to FrederikSchlemmer/angular that referenced this pull request Jan 3, 2019
… ngfactory & ngsummary files (angular#25604)

Workaround was added in angular#25335. It was necessary for .ngfactory & .ngsummary files to have proper AMD module names starting with @angular when building angular downstream from source using Bazel. The underlying issue has been resolved in the compiler and these files now get proper AMD module names without the need for this workaround. The workaround had an unexpected consequence angular/angular-cli#11835 which is fixed by its removal.

PR Close angular#25604
@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 13, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng serve --aot fail after file change
6 participants