-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add HarmSeverity.HARM_SEVERITY_UNSPECIFIED
#8830
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 59681b9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
HarmSeverity.HARM_SEVERITY_UNSPECIFED
HarmSeverity.HARM_SEVERITY_UNSPECIFIED
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So for context, we removed all the UNSPECIFIEDs in #8514 and you can look at the linked gDoc in that PR to see where that was decided - was that incorrect? Should we put them all back? Or only this one?
I didn't know this, thanks for bringing it up- I'll hold off on adding this for now and get back to you on whether we actually want to bring these enum values back. |
Add
HarmSeverity.HARM_SEVERITY_UNSPECIFIED
. Will serve as a fallback for whenHarmSeverity
is undefined in the future.This is a part of the proto.