-
Notifications
You must be signed in to change notification settings - Fork 26.2k
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
build(bazel): remove workaround no longer needed for module names for ngfactory & ngsummary files #25604
Conversation
You can preview 81998de at https://pr25604-81998de.ngbuilds.io/. |
For reference: the workaround was added in #25335 |
There was a problem hiding this 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.
81998de
to
c4b36a9
Compare
You can preview c4b36a9 at https://pr25604-c4b36a9.ngbuilds.io/. |
… 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
@alexeagle I think you said we also need another test for this |
… 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
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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.