angular_components contains multiple public libraries named the same, breaking dartdoc assumptions #1526
Labels
customer-google3
Issues originating from or important to Angular
P1
A high priority bug; for example, a single project is unusable or has many test failures
@kwalrath
Doing some testing for #1524 and noticed that angular_components now throws asserts in checked mode because of multiple public libraries having the same name.
Some examples of this:
The assert is not new, but while I was off on dart2now it had been a while since I had run angular2_components myself.
The consequence of this (assuming you're not in checked mode) is only one of the identically named libraries will show up in indexes and many links, with a lot of confusing internal linkage to and from elements in these libraries.
Proposed solution is to detect this situation and write libraries with name conflicts to different directories.
The text was updated successfully, but these errors were encountered: