Moderation Omni - New Categories (Illicit*) support. #495
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
|
Thanks @iBotPeaches for the PR 🥳 |
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.
What:
Description:
The Omni Moderation models were released, thus deprecating the older models (now referred to as Legacy). This introduced the
illicitandillicit/violentmoderation category, but ONLY for Omni. This presented an issue as this library iterated all known types and assumed all models will have it.Now we only set a Category if we have it and thus support partial support of Omni Moderation.
Ref: https://platform.openai.com/docs/guides/moderation
This does NOT add support for the new
category_applied_input_typesfield.