fix: locale-specific formatting due to MessageFormat.format()#1390
Merged
jfallows merged 1 commit intoaklivity:developfrom Jan 31, 2025
Merged
fix: locale-specific formatting due to MessageFormat.format()#1390jfallows merged 1 commit intoaklivity:developfrom
MessageFormat.format()#1390jfallows merged 1 commit intoaklivity:developfrom
Conversation
jfallows
approved these changes
Jan 31, 2025
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
2 participants
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.
When we have a schema ID (int), that's more than 3 digit, catalog handler unable to pull schema.
Cause:
MessageFormat.format() treats numbers according to locale-specific formatting rules. By default, it inserts a thousands separator (comma in some locales) when formatting numbers larger than 999.
Fixes #1391