microsoft / microsoft/AdaptiveCards

Input.ChoiceSet input validation - min and max

Open
#5,146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Design Discussion - Needed Request
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

What platform is your feature request related to? (Delete other platforms).
All Platforms

Is your feature request related to a problem? Please describe.
Currently there's no way to specify min or max number of elements that can be picked for an Input.ChoiceSet field in multi-select mode. This is a requirement we have in case of dynamic type ahead control (#3924) as well.

Describe the solution you'd like
Allow min and max attributes to be specified by card authors so that validation happens before submitting a form in Adaptive card.

Describe alternatives you've considered
The current alternative is to do the validation on service side and reject any requests after submitting a form in the adaptive card.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Input.ChoiceSet definition in the Adaptive Cards Explorer and review the related dynamic type-ahead issue #3924. Determine how card authors should express min and max for multi-select choices, then trace validation before form submission across the supported platforms. Done means both limits are accepted and enforced consistently before submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.