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

Clarify error handling and fix normative requirements #785

Closed
aphillips opened this issue May 8, 2024 · 1 comment
Closed

Clarify error handling and fix normative requirements #785

aphillips opened this issue May 8, 2024 · 1 comment
Labels
errors Issues related to the errors section of the spec LDML46 LDML46 Release (Tech Preview - October 2024)

Comments

@aphillips
Copy link
Member

In this comment I noted that the current spec contains untestable normative requirements about certain types of error (such as emitting syntax/data model errors "as early as possible"). My proposal includes changing the text:

- During selection and formatting,
- _expression_ handlers MUST only emit _Message Function Errors_.
+ _Syntax Errors_ and _Data Model Errors_ can always be detected during message parsing or processing.
+ (Other categories of error can sometimes be detected using validation tools.)
+
+ _Resolution Errors_ can be detected during _variable_, _function_, or _markup_ resolution.
+
+ _Message Function Errors_ apply to _selection_ or _formatting_
+ and include errors detected during the evaluation of an
+ _expression_ or during the execution of a _function_.
@aphillips aphillips added errors Issues related to the errors section of the spec LDML46 LDML46 Release (Tech Preview - October 2024) labels May 8, 2024
@aphillips
Copy link
Member Author

This has been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
errors Issues related to the errors section of the spec LDML46 LDML46 Release (Tech Preview - October 2024)
Projects
None yet
Development

No branches or pull requests

1 participant