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

Upgrade V6 SDK Generator Version for Form Recognizer #13360

Merged
merged 1 commit into from
Jan 25, 2021

Conversation

sarangan12
Copy link
Member

The last V6 SDK version that is used to generate Form Recognizer is 6.0.0-dev.20201113.1. This PR is to upgrade the V6 SDK version to the latest 6.0.0-dev.20210121.2 version.

@jeremymeng Please review and approve.

@joheredi @ramya-rao-a FYI.......


// @public
export type Language = "en" | "es" | "de" | "fr" | "it" | "nl" | "pt" | "zh-Hans" | string;
export const enum KnownKeyValueType {
// (undocumented)
Copy link
Member Author

Choose a reason for hiding this comment

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

This (undocumented) is part of the generated code that comes from the swagger. And Adding documentation for enum values does not make much sense. So, I think this is acceptable.

@witemple-msft
Copy link
Member

/azp run js - ai-form-recognizer - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@witemple-msft witemple-msft left a comment

Choose a reason for hiding this comment

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

Seems reasonable to me. It would be nice if we could have documentation on the enum variants, even a simple automatically generated one, but I agree that it's not that big of a deal as long as the enum itself has documentation.

I do wonder about the discoverability of the KnownKeyValueType enum (and its friends). At the least, I'm going to create an issue to add usage of these enums to samples for the next preview.

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

Successfully merging this pull request may close these issues.

2 participants