Skip to content

Conversation

@bojunehsu
Copy link
Member

Data Plane API Specification Update Pull Request

Content Understanding 2025-11-01 GA

API Info: The Basics

  • Link to API Spec engagement record issue:

Is this review for (select one):

  • a private preview
  • a public preview
  • GA release

Change Scope

This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

  • Design Document:
  • Updated paths:

@github-actions
Copy link

github-actions bot commented Nov 15, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
    To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
  • ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.


Comment generated by summarize-checks workflow run.

@github-actions github-actions bot added data-plane TypeSpec Authored with TypeSpec VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required labels Nov 15, 2025
@github-actions
Copy link

github-actions bot commented Nov 15, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
TypeSpec ContentUnderstanding
Java com.azure:azure-ai-contentunderstanding

yungshinlintw and others added 3 commits November 18, 2025 15:13
* MIGRATE SDK changes from azure-rest-api-specs-pr:

- Updated ContentUnderstandingClient interface to flatten operations and enhance naming conventions.
- Renamed ContentAnalyzer's status field to ResourceStatus for better clarity.
- Introduced StringEncoding union for encoding formats in AnalyzeParameters.
- Adjusted tspconfig.yaml to enable Java support and ensure proper emission of client libraries.

* PYTHON-SDK-FEEDBACK:
Add fieldType and inputRange renaming for clarity in ContentUnderstandingClient

* SDK-PYTHON: Hide string_encoding parameter in Python SDK and clarify string indexing behavior

* Move operation renames into interface definition

* PR Comments:
- Comment out emitters in emit to avoid dependency in this repo
- Move internal def of getRestul and getOperationStatus to client.tsp
- Merge operation rename in interface
- rename createAnalyzer

* Fix incorrect name in listAnalyzers renaming for .NET

* Fix typo in deleteAnalyzer method name in ContentUnderstandingClient interface
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data-plane TypeSpec Authored with TypeSpec VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants