Implement SEP-1330: Standards-compliant enum schemas for elicitation (#969)
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: stephentoub <2642209+stephentoub@users.noreply.github.com> Co-authored-by: Stephen Toub <stoub@microsoft.com>
This commit is contained in:
parent
3f39ba7936
commit
83098e7cc0
1 changed files with 963 additions and 20 deletions
|
|
@ -51,7 +51,7 @@ public sealed class ElicitResult : Result
|
|||
/// </para>
|
||||
/// <para>
|
||||
/// Values in the dictionary should be of types <see cref="JsonValueKind.String"/>, <see cref="JsonValueKind.Number"/>,
|
||||
/// <see cref="JsonValueKind.True"/>, or <see cref="JsonValueKind.False"/>.
|
||||
/// <see cref="JsonValueKind.True"/>, <see cref="JsonValueKind.False"/>, or <see cref="JsonValueKind.Array"/> (for multi-select enums).
|
||||
/// </para>
|
||||
/// </remarks>
|
||||
[JsonPropertyName("content")]
|
||||
|
|
|
|||
Loading…
Reference in a new issue