Better handling of negative elements in enum #40679
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #39065; fixes a warning added in #36380 that fires a bit too often. Adds a more descriptive warning, and logs it only when there's actually a conflict.
An example of where this is annoying is in our app:
Results in this warning every time the app boots:
An enum element in MobileDeviceToken uses the prefix 'not_'. This will cause a conflict with auto generated negative scopes.
Even though there isn't actually anything we need to change.