InteractionService should expose `InteractionInput`-based APIs for requesting confirmation
Open
area-cli
interaction-service
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
The `InteractionService` currently models requests for confirmation as `MessageBoxInteractions`.
https://github.com/dotnet/aspire/blob/6ab1e17a1888f3e0b3ebbbd83269088d824e1baf/src/Aspire.Hosting/ApplicationModel/InteractionService.cs#L36-L44
We should consider modeling confirmation as an `InputInteraction` and add confirmation to the `InputType` enum to make the implementation play more nicely with CLI-based UIs where both confirmations and text-based inputs flow through the same pipeline.
Related to this, we should consider renaming certain APIs (like `InputsDialogInteractionOptions`) to remove assumptions about the type of UI that is used to present an interaction.
cc: @JamesNK @mitchdenny
Contributor guide
Assessment
This issue has not been assessed yet.