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

[feature request] provide language-independent identifiers for errors #43

Open
DerekNonGeneric opened this issue Jul 21, 2022 · 0 comments
Labels
enhancement New feature or request i18n Related to internationalization
Milestone

Comments

@DerekNonGeneric
Copy link
Member

According to the Internationalization Best Practices for Spec Developers published by W3C Internationalization Working Group, we should be providing language-independent identifiers for errors.

It seems like the code property on each of our error instances would be the most appropriate place for this, but we are currently using constant-case identifiers (e.g., ERR_MISSING_OPTION like Node.js core) for this. Depending on how these errors are being checked at run-time, and if we want to be able to maintain interop with Node.js in the future, it may be worthwhile to use a different property for the language-independent identifier, which will most likely be composed strictly of digits.

@DerekNonGeneric DerekNonGeneric added enhancement New feature or request i18n Related to internationalization labels Jul 21, 2022
@DerekNonGeneric DerekNonGeneric added this to the Version 3.0 milestone Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request i18n Related to internationalization
Projects
None yet
Development

No branches or pull requests

1 participant