Skip to content

Conversation

@radhgupta
Copy link
Member

@radhgupta radhgupta commented Dec 18, 2025

Contributing to the Azure SDK

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.

For specific information about pull request etiquette and best practices, see this section.

Resolved: #54491

@radhgupta radhgupta changed the title Migrate Azure.AI.ContentSafety to new Generator Migrate Azure.AI.ContentSafety to new Emitter Dec 18, 2025
@github-actions
Copy link

github-actions bot commented Dec 18, 2025

API Change Check

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

Azure.AI.ContentSafety

Copy link
Member

@jorgerangel-msft jorgerangel-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -1,457 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets move these docs out of the generated folder vs deleted them since the new generator doesn't support doc generation yet.

Copy link
Member

@JonathanCrd JonathanCrd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a couple of comments.

There are other task that are still needed for this PR:

  1. There will be changes in the API, you have to regenerate them by running:
eng\scripts\Export-API.ps1 contentsafety
  1. Test are failing due to "missing" recordings, but by looking at the CI logs this is actually a bug where the request URL is malformed with a duplicated path component, here.

@radhgupta radhgupta force-pushed the migrateContentSafety branch from 56469b9 to d84a42a Compare January 8, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate Azure.AI.ContentSafety to new code Generator

3 participants