forked from Azure/azure-rest-api-specs
-
Notifications
You must be signed in to change notification settings - Fork 4
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
GetModels API Update - Add Summary query option #3
Open
ramparab
wants to merge
87
commits into
master
Choose a base branch
from
update_getmodels_summary_option
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix paths of methods (add custom) and fix path of hosttemplate
Update FormRecognizer.json
FR Receipt Doc, API updates
…g the documentation to a short paragraph
krishnand
reviewed
Jul 31, 2019
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.
Can you mention in the relevant description fields that GetModels will now return models that are not successfully trained as well.
ramparab
pushed a commit
that referenced
this pull request
Mar 25, 2020
* Add encryption scope API to 2019-06-01. Add encryption scope API to 2019-06-01. * Address CI failures. * Fix CI failures #2. * Address CI failures #3. Co-authored-by: Anthony Kunnel Jose <[email protected]>
ramparab
pushed a commit
that referenced
this pull request
Mar 25, 2020
* 2019-08-09-preview * spell out networks * username and credential needed to add an IdentitySource * post listAdminCredentials * standardize on username, password, nsxt and vcenter * add nsxt to custom-words.txt * default cluster does not have provisioningState * it extends DefaultClusterProperties * add Circuit expressRoutePrivatePeeringID * back out some minor changes for sdk generation * identitySources and Circuit authorizations are updateable * add PrivateClouds_ListInSubscription * Long running operation for Clusters_Delete (#1) * npm run prettier * location for all resources (#2) * Revert "location for all resources (#2)" (#3) This reverts commit 432e37b. * add description TODOs * example is PrivateClouds_Update * require body in PrivateClouds_Update * replaced TODOs with descriptions * spellcheck * "x-ms-secret": true * Revert ""x-ms-secret": true" This reverts commit 3358dff. Co-authored-by: Andrew Ulliani <[email protected]> Co-authored-by: Eugene Tolmachev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.