You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-dotnet-sdk-migration-version-10.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Version 10 of the Azure Search .NET SDK targets the latest generally available v
31
31
32
32
* Introduction of two new skills - [Conditional skill](cognitive-search-skill-conditional.md) and [Text Translation skill](cognitive-search-skill-text-translation.md).
33
33
*[Shaper skill](cognitive-search-skill-shaper.md) inputs have been restructured to accommodate consolidation from nested contexts. For more information, see this [example JSON definition](https://docs.microsoft.com/azure/search/cognitive-search-skill-shaper#scenario-3-input-consolidation-from-nested-contexts).
34
-
* Addition of 2 new [field mapping functions](search-indexer-field-mappings.md):
34
+
* Addition of two new [field mapping functions](search-indexer-field-mappings.md):
* On certain occasions, errors and warnings that show up in [indexer execution status](https://docs.microsoft.com/rest/api/searchservice/get-indexer-status) can have additional details that help in debugging. `IndexerExecutionResult` has been updated to reflect this behavior.
@@ -63,7 +63,7 @@ There are several breaking changes in version 10 that may require code changes i
63
63
64
64
The definition of the [Custom Web API skill](cognitive-search-custom-skill-web-api.md) was incorrectly specified in version 9 and older.
65
65
66
-
The model for `WebApiSkill` specified `HttpHeaders` as an object property that _contains_ a dictionary. Creating a skillset with a `WebApiSkill` constructed in this manner would result in an exception because the REST API would consider the request badly formed. This has been corrected, by making `HttpHeaders`**a top-level dictionary property** on the `WebApiSkill` model itself - which is considered a valid request from the REST API.
66
+
The model for `WebApiSkill` specified `HttpHeaders` as an object property that _contains_ a dictionary. Creating a skillset with a `WebApiSkill` constructed in this manner would result in an exception because the REST API would consider the request badly formed. This issue has been corrected, by making `HttpHeaders`**a top-level dictionary property** on the `WebApiSkill` model itself - which is considered a valid request from the REST API.
67
67
68
68
For example, if you previously attempted to instantiate a `WebApiSkill` as follows:
69
69
@@ -136,13 +136,13 @@ var skillset = new Skillset()
0 commit comments