-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add :test:function, :test:select, and :test:format function definitions #769
Conversation
As discussed during yesterday's call, it'd be better for the functions to more clearly depart from e.g. I also added details for what happens when a |
Co-authored-by: Addison Phillips <[email protected]>
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.
The proposed :test:function
appears super minimal, which seems good to me. I agree this is useful for testing, giving a way to avoid locale-dependent output. I'll defer on the exact spec text and scope.
#### Options | ||
|
||
The only _option_ `:test:function` recognizes is `fd`, | ||
a _digit size option_ for which only `0` and `1` are valid values. |
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.
Linkifying digit size just as "Number Operand" is being linkified 5 lines above. Helps short circuit questions like mine for the reader.
a _digit size option_ for which only `0` and `1` are valid values. | |
a [_digit size option_](/spec/registry.md#digit-size-options) for which only `0` and `1` are valid values. |
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.
Underscore italics are linkified when the spec is turned into HTML. That's what this is for.
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.
LGTM
CC @mradbourne
Given that we shouldn't rely on
:number
and:datetime
producing exact results but we still want to ensure that our interfaces with them work, let's add:test:number
and:test:plural
as well-defined functions intended for tests only, with exactly defined behaviour.This PR could be extended with test cases making use of these, but I figured it'd be more useful to consider the general case first, esp. in order to avoid conflicting with #767.