Adding custom non-batched return types for non-batch calls #6992
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An update to v4.0.0 which has not been published yet (hence the same version number).
Adding custom non-batched return types for non-batch calls simplifying the callee code.
Previously, the non-batch methods would send a single document for analysis but return a batch response that can only contain a single document. Instead, we now return a single response from these methods and unwrap the list for you. The same is done for any potential errors and statistics responses.
Previously:
And now:
This is a simplification over a batch service REST API that hasn't changed. Will be mainly used for example/documentation purposes.