Skip to content

Number format in ICU4X: add known issues and unsupported rounding modes #470

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sven-oly
Copy link
Collaborator

This reclassifies all but one test failure in ICU4X number format. That test will be handled when PR #458 is submitted.

Comment on lines 147 to 155
# For datetime_fmt, is the format type "standard"?
at_strings = [' at', 'เวลา', ' هـ']
if actual == expected:
return None
if actual.replace(' at', ',') == expected:
return knownIssueType.datetime_fmt_at_inserted
for at_string in at_strings:
if actual.replace(at_string, ',') == expected:
return knownIssueType.datetime_fmt_at_inserted
return None

Copy link
Member

Choose a reason for hiding this comment

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

Datetime pollution?

# Number format known issues
def check_number_fmt_issues(test):
input = test['input_data']['input']
if 'result' in test and test['result'] == '-' and abs(float(input)) < 1.0:
Copy link
Member

Choose a reason for hiding this comment

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

Suggestion: this should check for ICU4X, Compact, and abs(float(input)) < 1.0

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants