I thought I had resolved this in #2087, but I just ran into another case of this Angular ID collision issue in this build. This time rather than being a collision for components AbsoluteSimpleLinkCmp and RelativeLinkCmp, it's a collision between two different definitions of RelativeLinkCmp:
Failed: NG0912: Component ID generation collision detected. Components 'RelativeLinkCmp' and 'RelativeLinkCmp' with selector 'link-cmp' generated the same component ID. To fix this, you can change the selector of one of those components or add an extra host attribute to force a different ID. Find more at https://angular.io/errors/NG0912
👩💻 Implementation
Uniquified each link-cmp selector by appending :not([nimble-unused-X]).
🧪 Testing
None
✅ Checklist
[x] I have updated the project documentation to reflect my changes or determined no changes are needed.
Pull Request
🤨 Rationale
I thought I had resolved this in #2087, but I just ran into another case of this Angular ID collision issue in this build. This time rather than being a collision for components
AbsoluteSimpleLinkCmpandRelativeLinkCmp, it's a collision between two different definitions ofRelativeLinkCmp:👩💻 Implementation
Uniquified each
link-cmpselector by appending:not([nimble-unused-X]).🧪 Testing
None
✅ Checklist