Skip to content

Conversation

JeanMeche
Copy link
Member

It caught several legitimate issues.
In the cases I wasn't sure, I just disabled the rule.

fixes #45843

@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Aug 29, 2025
@JeanMeche JeanMeche requested a review from mmalerba August 29, 2025 16:04
@ngbot ngbot bot added this to the Backlog milestone Aug 29, 2025
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

Can we add some documentation somewhere of why this is not desirable? It seems like in some situations that duplicate enum values could be very useful.

@JeanMeche JeanMeche force-pushed the noduplicate-enum branch 2 times, most recently from f2246c3 to f7ce8ba Compare August 29, 2025 16:31
It caught several legitimate issues.
In the cases I wasn't sure, I just disabled the rule.

fixes angular#45843
@pullapprove pullapprove bot requested review from atscott and kirjs August 29, 2025 16:51
@JeanMeche
Copy link
Member Author

I think the diff is a bit self explantory, it's not the first time we have colliding Error codes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build & ci Related the build and CI infrastructure of the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable the no-duplicate-enum-values TSLint rule for the FW repo
2 participants