-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
ICU-22762 MF2: Add methods to control error handling behavior #3083
Conversation
0e5f313
to
e60d668
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
e60d668
to
db75954
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
1657aff
to
32f5ca3
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
also cc @srl295 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOKTM
@richgillam @echeran Per a suggestion from @mihnita on the design doc, I added 7e421d4 -- all that does is move the enum definition out of the builder class into the I didn't change the design doc because I didn't want to edit what was already accepted by TC; thus I'm just making this change in the code but calling attention to it being different from the design doc. |
At some point, I'm going to have to go through and promote all the new APIs from I don't object to the actual change, but I think you want to update the proposal to match what you're checking in, and you should probably either go through API review again (hopefully it'd just be a rubber stamp) or at least notify everyone via the |
OK, that makes sense. I changed the design doc to match this code, and emailed the icu-design list. |
7e421d4
to
235e646
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
I added a note for this into the ICU 76 API proposal status doc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some concerns but I am not going to block merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOKTM
Add MessageFormatter::Builder::setErrorHandlingBehavior() method and a new enum type MessageFormatter::UMFErrorHandlingBehavior to denote strict or best-effort behavior. The reason for adding a single method that takes an enum is to allow for the possibility of more error handling modes in the future. Co-authored-by: Markus Scherer <[email protected]>
b5e890a
to
3cc5232
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
Checklist