microsoft / microsoft/AdaptiveCards
Ensuring a submit action can only be done once
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Is there any mechanism to ensure a submit action is only done once from a card? Perhaps a mechanism to disable / hide after first successful use would be useful. Without this, bots have to incorporate logic to try to handle multiple submissions on the form even after the user may have moved farther along in the conversation. We have run into UX issues with this with several deployments, primarily using the web channel.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue discussion and its examples of repeated submissions, focusing on the reported web-channel UX problems. No source files, tests, or entry points are identified in the issue, so first locate the submit-action handling for web cards and review the existing behavior. Done should mean a card cannot submit again after a successful use, with the behavior defined for affected deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100