[Search] Answers Should be Defined as a String, Not an Enum

[alzimmermsft]

The Answers definition, both the SearchOptions query parameters and SearchRequest JSON property, should be redefined as just a string type and not an enum type.

The reason for this is that with the current definition these will only be able to support passing the defined enum value, currently none or extractive, and won't be able to support passing the additional count-<# of answers> modifier to change the search from only returning a single answers for each one (documentation for the search request).

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @brjohnstmsft, @bleroy, @tjacobhi, @MarkHeff, @miwelsh.

Issue Details

---

The Answers definition, both the SearchOptions query parameters and SearchRequest JSON property, should be redefined as just a string type and not an enum type.

The reason for this is that with the current definition these will only be able to support passing the defined enum value, currently none or extractive, and won't be able to support passing the additional count-<# of answers> modifier to change the search from only returning a single answers for each one (documentation for the search request).

Author:	alzimmermsft
Assignees:	-
Labels:	Search, Service Attention
Milestone:	-