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

The Case for Globally Namespaced Class Names in Angular Post Optimization #16637

Closed
fireflysemantics opened this issue Jan 10, 2020 · 1 comment
Closed

Comments

@clydin

This comment has been minimized.

Copy link
Member

@clydin clydin commented Jan 11, 2020

Thank you for your interest in this issue. However, as discussed in the referenced issue, class identifiers are not guaranteed to be globally unique regardless of any optimization transformations.
Even if this were not the case, a single application can span hundreds of output JavaScript files and the optimization pipeline is both multi-threaded and multi-process. Implementing such behavior within the optimization pipeline would be highly non-trivial, add a large amount of complexity, and create the potential for both build-time performance and output file size regressions.

@clydin clydin closed this Jan 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.