-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various Search model properties need to be authored as x-nullable: true #10226
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @brjohnstmsft, @bleroy, @tjacobhi, @MarkHeff, @miwelsh. |
Thanks for reporting this @heaths. If I had to guess how we got into this state, it might be because we incorrectly assumed that I'll fix all the core Search instances of this. @bleroy, can you please fix the indexer- and skillset-related instances? |
@brjohnstmsft Sure. |
This isn't complete. When referencing in commits, make sure a word separates keywords like "fixed", "resolves", etc. until complete so it doesn't get auto-closed. |
…zure#10293) * [Azure Cognitive Search] Add missing x-nullable annotations, part 2 Fixes Azure#10226 * [Azure Cognitive Search] Fix example causing validation error Co-authored-by: Bruce Johnston <brjohnst@microsoft.com>
We're finding in the Azure Cognitive Search SDK for .NET that quite a few model properties need to be authored as x-nullable because the service implementation may return them as null.
See https://github.com/Azure/azure-sdk-for-net/blob/80ff0d075221715e3eb8e8645eac2cef203e7c8f/sdk/search/Azure.Search.Documents/src/autorest.md#add-nullable-annotations for a current list. Should we add more, we can open a new issue with the difference. If possible, it would be great if the service team could validate the swagger authoring against the service implementation.
This should be fixed in 2020-06-30 and any current preview being updated.
The text was updated successfully, but these errors were encountered: