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

Luis swagger fixes #5416

Merged
merged 6 commits into from
Mar 19, 2019
Merged

Luis swagger fixes #5416

merged 6 commits into from
Mar 19, 2019

Conversation

diberry
Copy link
Contributor

@diberry diberry commented Mar 18, 2019

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#4327

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-js

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-js#1642

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#4389

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Mar 18, 2019

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@@ -2605,7 +2648,7 @@
},
"/apps/{appId}/querylogs": {
"get": {
"description": "Gets the query logs of the past month for the application.",
"description": "Gets thelogs of the past month's endpoint queries for the application.",
Copy link
Contributor

Choose a reason for hiding this comment

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

thelogs -> the logs

@@ -9214,7 +9263,7 @@
"description": "A list of comma-separated values."
},
"isExchangeable": {
"description": "An exchangeable phrase list feature are serves as single feature to the LUIS underlying training algorithm. It is used as a lexicon lookup feature where its value is 1 if the lexicon contains a given word or 0 if it doesn’t. Think of an exchangeable as a synonyms list. A non-exchangeable phrase list feature has all the phrases in the list serve as separate features to the underlying training algorithm. So, if you your phrase list feature contains 5 phrases, they will be mapped to 5 separate features. You can think of the non-exchangeable phrase list feature as an additional bag of words that you are willing to add to LUIS existing vocabulary features. Think of a non-exchangeable as set of different words. Default value is true.",
"description": "An exchangeable phrase list feature are serves as single feature to the LUIS underlying training algorithm. It is used as a lexicon lookup feature where its value is 1 if the lexicon contains a given word or 0 if it doesn’t. Think of an exchangeable as a synonyms list. A non-exchangeable phrase list feature has all the phrases in the list serve as separate features to the underlying training algorithm. So, if you your phrase list feature contains 5 phrases, they will be mapped to 5 separate features. You can think of the non-exchangeable phrase list feature as an additional bag of words that you are willing to add to LUIS existing vocabulary features. Think of a non-exchangeable as set of different words. Default value is true.",,
Copy link
Contributor

Choose a reason for hiding this comment

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

Double comma at the end

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nschonni what tool did you use to find these issues?

Copy link
Contributor

Choose a reason for hiding this comment

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

Opening the content in VS Code caught the double comma at the end as an error. I've got an running PR to add a cSpell dictionary with #4836. Right now, I just open that branch and past the code into an existing file to see the issues though.

@jhendrixMSFT
Copy link
Member

Please note this contains breaking changes in a swagger marked as stable which is discouraged.

@shahabhijeet
Copy link
Member

@jhendrixMSFT .NET SDK does not support multiple RPs as of now.
I think we should have two separate PRs for each RP.
If one SDK generation fails and other succeeds, it's challenging to let the user know what exactly failed as there are only 1 job created for 1 RP.
But if you still would like to merge, go ahead, .NET SDK has still not enabled multiple RPs.
Plus this is data plane SDK

@diberry
Copy link
Contributor Author

diberry commented Mar 19, 2019

@jhendrixMSFT @shahabhijeet @cahann @nebadr

This PR has changes from the service team, provided by @nebadr and changes to the descriptions I provided as docs member.

I'll remove the runtime changes so it is only 1 file being changed.

Are there specific issues about the service team's changes that you need addressed?

@diberry
Copy link
Contributor Author

diberry commented Mar 19, 2019

Runtime broken out into different PR #5424

@diberry diberry mentioned this pull request Mar 19, 2019
5 tasks
adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request Mar 19, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5416'
REST Spec PR Author 'diberry'
REST Spec PR Last commit
@adxsdknet
Copy link

Automation for azure-sdk-for-net

A PR has been created for you:
Azure/azure-sdk-for-net#5511
.NET SDK Commits:
adxsdknet/azure-sdk-for-net@39f8c63

@jhendrixMSFT
Copy link
Member

@AutorestCI regenerate azure-sdk-for-go

@jhendrixMSFT jhendrixMSFT merged commit 4cd8984 into Azure:master Mar 19, 2019
dsgouda pushed a commit to Azure/azure-sdk-for-net that referenced this pull request Mar 21, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5416'
REST Spec PR Author 'diberry'
REST Spec PR Last commit
@dsgouda dsgouda mentioned this pull request Mar 26, 2019
5 tasks
mentat9 pushed a commit to mentat9/azure-sdk-for-net that referenced this pull request Jun 10, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5416'
REST Spec PR Author 'diberry'
REST Spec PR Last commit
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.

7 participants