New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strings: reverted to case-sensitive sorting for keys #890
base: develop
Are you sure you want to change the base?
Strings: reverted to case-sensitive sorting for keys #890
Conversation
1b6e7c2
to
233a4b2
Compare
233a4b2
to
cea4747
Compare
19ca485
to
cf4273e
Compare
cf4273e
to
cb0617c
Compare
cb0617c
to
026aa23
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Yeah this is a very well known issue with Anyway, this has little to do with SwiftGen 😅 @grigorye's original issue was with 2 keys with the same value (differing only in case). Honestly not a realistic situation, curious if anyone has a good test case for this. And if so, please try out these changes. |
This should fix #891, as well as slightly affect the performance due to no need to lowercase keys on every comparison during the sorting.