Skip to content
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

Merged
merged 3 commits into from
Sep 17, 2021

Conversation

deyaaeldeen
Copy link
Member

Issue: #17697

These renames were requested by the archboard.

@@ -17,7 +17,7 @@ export interface GetSchemaPropertiesOptions extends OperationOptions {
}

// @public
export const enum KnownSerializationType {
export const enum KnownSchemaFormat {
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

@xirzec xirzec left a comment

Choose a reason for hiding this comment

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

LGTM

@deyaaeldeen deyaaeldeen merged commit 6a350c6 into Azure:main Sep 17, 2021
@deyaaeldeen deyaaeldeen deleted the schema-registry/renames branch September 17, 2021 22:33
@nguerrera
Copy link
Contributor

I was out when this came in, but just noting that I looked at this now and it looks good to me too. 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants