Skip to content
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

Error handling for expected likely subtag errors #205

Open
echeran opened this issue Mar 25, 2024 · 0 comments
Open

Error handling for expected likely subtag errors #205

echeran opened this issue Mar 25, 2024 · 0 comments

Comments

@echeran
Copy link
Collaborator

echeran commented Mar 25, 2024

Some of the test cases for likely subtags are supposed to fail. The source test data encodes this information.

We need to decide a canonical error representation during our testing. CLDR defines ways to handle such an error:

Signalling an error can be done in various ways, depending on the most consistent approach for APIs in the module. For example:

raise an exception
return an error value (such as null)
return the input (with missing fields)
return the input, but "Zzzz", and/or "ZZ" substituted for empty fields.
"und"

Whichever way we decide to handle it, we need to update our executors, which will also hopefully decrease the number of test failures.

@echeran echeran added this to the 2024 Q2 milestone Mar 25, 2024
@echeran echeran removed the 2024 Q2 label Mar 25, 2024
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

No branches or pull requests

1 participant