Skip to content

Should Input.Number value accept a string? #3287

@v-kydela

Description

@v-kydela

Issue

Every version of the schema I've seen says the value property of Input.Number only accepts a number.

image

However, I've tried using a string for the value in both Web Chat and Microsoft Teams and they work. Both of these inputs render the same:

{
  "type": "Input.Number",
  "id": "id-number",
  "value": 7,
  "placeholder": "Placeholder text"
},
{
  "type": "Input.Number",
  "id": "id-numberString",
  "value": "7",
  "placeholder": "Placeholder text"
},

Which is correct? Should the schema say "number, string" instead of just number? Or are those renderers operating contrary to the schema?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-InconsistencyBugs around renderer inconsistencies across different platformsBug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions