reflect decision to have SO decorator as a reference implementation in samples

This commit is contained in:
SergeyMenshykh
2026-02-10 19:31:04 +00:00
Unverified
parent 8635783cd2
commit 04abdbdc5d
+3 -1
View File
@@ -653,4 +653,6 @@ For cross-cutting aspects, the `useJsonSchemaResponseFormat` parameter will not
For handling primitives and array types, option 3 was selected: wrap only for `RunAsync<T>` and do not wrap the schema provided via `ResponseFormat`.
This avoids the issues described in the Approach 1 section note.
Finally, the `StructuredOutputAgent` decorator will be implemented to provide structured output capabilities to agents without native SO support.
Finally, it was decided not to include the `StructuredOutputAgent` decorator in the framework, since the reliability of producing structured output via an additional
LLM call may not be sufficient for all scenarios. Instead, this pattern is provided as a sample to demonstrate how structured output can be achieved for agents without native support,
giving users a reference implementation they can adapt to their own requirements.