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

Fix typo in enum modes in spell check json #2488

Merged
merged 1 commit into from
Feb 13, 2018

Conversation

sarangan12
Copy link
Member

@sarangan12 sarangan12 commented Feb 13, 2018

This is a minor fix to the spellcheck.json. The service expects "proof"/"spell". But, it is added in the swagger file as "Proof"/"Spell". This PR is to fix it.

If the SDKs have been released already, this will not be a breaking change. But more as a bug fix.

@ashku-ms @olydis Please review and approve

@AutorestCI
Copy link

AutorestCI commented Feb 13, 2018

Automation for azure-sdk-for-python

Was unable to create SDK azure-sdk-for-python PR for this closed PR.

@AutorestCI
Copy link

AutorestCI commented Feb 13, 2018

Automation for azure-sdk-for-go

Was unable to create SDK azure-sdk-for-go PR for this closed PR.

Copy link
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

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

Please, provide examples next time.

@sergey-shandar sergey-shandar merged commit dd6b0da into Azure:master Feb 13, 2018
@azuresdkciprbot
Copy link

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/cognitiveservices/data-plane/SpellCheck/readme.md
Before the PR: Warning(s): 0 Error(s): 1
After the PR: Warning(s): 0 Error(s): 1

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

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.

4 participants