Duplicate ID in TimeZoneInfo#114
Merged
mattjohnsonpint merged 3 commits intomattjohnsonpint:mainfrom Aug 7, 2022
Merged
Conversation
Contributor
Author
|
@mattjohnsonpint, do you have any comments regarding that? |
Owner
|
Thanks for the PR, and sorry for the delay. I changed the implementation slightly, to avoid a custom comparer. Also, I added a call to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With current implementation I face this issue:
According to https://referencesource.microsoft.com/#mscorlib/system/timezoneinfo.cs,2881 there could be 2 Time zone Id with same name but different case.
However, I clearly understand that registry key may not have subkeys with same name but different case. Yet this issue is reproducing. To mitigate this and prevent same issue in the future, it worth adding such distinct check.