-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Schema Registry] Apply Archboard requested renames #17720
Conversation
@@ -17,7 +17,7 @@ export interface GetSchemaPropertiesOptions extends OperationOptions { | |||
} | |||
|
|||
// @public | |||
export const enum KnownSerializationType { | |||
export const enum KnownSchemaFormat { |
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.
Why do we use "Known" here?
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.
It is a standard pattern in JS where we model extensible enums as strings and in their docstring we refer to a known enum that defines the possible values to use. This known enum does not show up anywhere else in the public surface.
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.
LGTM
I was out when this came in, but just noting that I looked at this now and it looks good to me too. 😁 |
Issue: #17697
These renames were requested by the archboard.