microsoft / microsoft/AdaptiveCards

Input.ChoiceSet changeAction

Open
#4,714 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Epic Feature
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Description

Open Issues

  • Confirm how this may be impacted with other inputs. DECISION: Might be weird with Input.Text, but we can cross that bridge when we get there.

  • What about setting focus on an element, etc. Perhaps an action collection design. DECISION: Not at this time

  • Can we allow a per-choice action? DECISION: Not at this time.

  • Do we need to delineate between server-side and client-side variations? DECISION: Server-based actions only for now

  • What is the final name if we do decide to delineate? DECISION: changeAction because it would work for Toggle.

Schema/spec

Property
Type
Required
Description
changeAction
Action
No
When specified, an the Action will be executed when a choice is made. Only supports Action.Submit and Action.Execute

Requirements

  1. This property only works when isMultiSelect is set to false

  2. Should work for any style (radio buttons, and drop downs)

Examples

{
   "type": "Input.ChoiceSet",
   "label": "Select a user",
   "isMultiSelect": false,
   "choices":  [
      { "title": "User 1", "value": "User1" },
      { "title": "User 2", "value": "User2" }
    ],
   "changeAction": {
      "type": "Action.Submit",
      "id": "userSelectAction"
   }
}

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

The issue names Input.ChoiceSet and its changeAction property but provides no implementation files, tests, or renderer entry points. Start by tracing Input.ChoiceSet schema and renderer handling, then determine how the stated single-select and style requirements are covered. Done means the schema and documented behavior support the specified server-side actions.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.