PromptPlus
|Adr-Plus Fields|Values Migrated | |–|–| |ADR|Controls vs Widgets separation| |Version|01| |Revision|01| |Scope|| |Domain|| |Created|Proposed (2026-07-24)| |Changed|Accepted (2026-07-24)| |Superseded||
# PromptPlus
## **ADR0007V01R01**
[](https://www.nuget.org/packages/PromptPlus)
[](https://opensource.org/licenses/MIT)
[](https://dotnet.microsoft.com/)
ADR0007V01R01 — Controls vs Widgets separation
Context
The library offers both interactive prompts (that read the keyboard and return a value) and output-only visual elements (banners, tables, progress). Mixing them under one factory blurs their very different lifecycles.
Decision
Split the surface into two factories:
PromptPlus.Controls— interactive elements that block, read input, and return aResultPrompt<T>via.Run().PromptPlus.Widgets— output/visual elements that render to the console and do not return a user value.
A type is a control if and only if it produces a ResultPrompt<T>.
Consequences
- Positive: the return contract makes the category unambiguous; discovery is guided by intent (interact vs display).
- Negative / trade-off: some elements (e.g. progress) could be argued either way; the “returns a result?” test resolves the ambiguity deterministically.