8000 What is the behavior of `:number` when passed an option with a non-integer value? · Issue #739 · unicode-org/message-format-wg · GitHub
[go: up one dir, main page]

Skip to content
What is the behavior of :number when passed an option with a non-integer value? #739
Closed
@catamorphism

Description

@catamorphism

The spec for the :number function refers to five different options whose values must be a non-negative integer, beginning with minimumIntegerDigits and continuing from there.

However, it's unspecified what the behavior should be when something that can't be coerced to a non-negative integer is passed in for the value of one of these options. (I also assume that "non-negative integer" should include strings that can be parsed as non-negative integers; otherwise, literals as option values wouldn't work.)

If the implementation of the :number function should signal an error, that's a problem because of #738 (there is no error type that really fits this case).

If the error handling is meant to be implementation-dependent, then I think the registry spec should say that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    LDML46LDML46 Release (Tech Preview - October 2024)blocker-candidateThe submitter thinks this might be a block for the next releasefunctionsIssue pertains to the default function set

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0