-
-
Notifications
You must be signed in to change notification settings - Fork 36
Clarify standalone
vs. open
vs. close
function/expression
#424
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
Comments
For completeness and ease of viewing, here's @aphillips's comment from the review thread linked above:
|
There are two requirements that I'd like to suggest, in line with @aphillips's comment:
These two requirements combined lead me to suspect that we should move the open/close syntax into the placeholder rather than bind it to the function name. |
I have a few thoughts on this:
|
This issue looks like it has been superseded by https://github.com/unicode-org/message-format-wg/blob/main/exploration/open-close-placeholders.md and #537 |
See: https://github.com/unicode-org/message-format-wg/pull/419/files#r1262730738
In adding definitions for open and close expressions (and their friend standalone), we found that we are underspecifying them. This is a placeholder to solve that.
The text was updated successfully, but these errors were encountered: