[Vertex AI] Refactor HarmCategory enum - #13686
Merged
Merged
Conversation
paulb777
approved these changes
Sep 20, 2024
andrewheard
force-pushed
the
ah/vertex-harmcategory
branch
from
September 23, 2024 14:39
b81e68f to
aa4058c
Compare
Contributor
Author
|
Rebased |
andrewheard
added a commit
that referenced
this pull request
Sep 24, 2024
# Conflicts: # FirebaseVertexAI/CHANGELOG.md
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
unspecifiedcase fromHarmCategorysince it should never be returned by the backend and should never be provided in a request.unknowncase would cover this anomalous scenario if it ever occurred.HarmCategoryenum out ofSafetySettingsince it is also used inSafetyRating.