Fix example title in ContentAnalyzers_DeleteResult.json #38877
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
Co-authored-by: bojunehsu <1988517+bojunehsu@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update to address feedback from review on Content Understanding GA PR
Fix example title in ContentAnalyzers_DeleteResult.json
Nov 19, 2025
bojunehsu
approved these changes
Nov 19, 2025
Copilot finished work on behalf of
bojunehsu
November 19, 2025 06:37
bojunehsu
merged commit b8cd664
into
paulhsu/ContentUnderstanding-2025-11-01
4 of 11 checks passed
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
bojunehsu
added a commit
that referenced
this pull request
Nov 20, 2025
* Initial commit of Content Understanding 2025-11-01 GA * Migrate the client SDK changes from azure-rest-api-specs-pr (#38839) * 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 * Remove preview versions. Add examples. * Fix PR checks * Fix example title in ContentAnalyzers_DeleteResult.json (#38877) * Initial plan * Fix example title: Change "Delete Analyzer" to "Delete Analysis Result" Co-authored-by: bojunehsu <1988517+bojunehsu@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: bojunehsu <1988517+bojunehsu@users.noreply.github.com> * Address review feedbacks. --------- Co-authored-by: Yung-Shin Lin <yslin@microsoft.com> Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: bojunehsu <1988517+bojunehsu@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.Addresses review feedback from #38821 on incorrect example title. The
ContentAnalyzers_DeleteResult.jsonexample incorrectly titled the operation as "Delete Analyzer" when it actually deletes an analysis result, not the analyzer itself.Changes
ContentAnalyzers_DeleteResult.jsonContentAnalyzers_GetResult.json("Get Analysis Result")ContentAnalyzers_Delete) vs. deleting an analysis result (ContentAnalyzers_DeleteResult)PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
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.
specification/ai/data-plane/ContentUnderstanding/stable/2025-11-01/examples/ContentAnalyzers_DeleteResult.jsonViewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Release planner
A release plan should have been created. If not, please create one as it will help guide you through the REST API and SDK creation process.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links
Getting help
write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.