Bump down version for Text Analytics v3.2-preview.1 to v3.1-preview.3#11388
Merged
tjprescott merged 62 commits intoAzure:masterfrom Oct 27, 2020
Merged
Bump down version for Text Analytics v3.2-preview.1 to v3.1-preview.3#11388tjprescott merged 62 commits intoAzure:masterfrom
tjprescott merged 62 commits intoAzure:masterfrom
Conversation
…w.1 to version 2018-05-01-privatepreview
…5-01-privatepreview
[Staging] Swagger Validation Report
️✔️ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-java - Release
|
azure-resource-manager-schemas - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
This was referenced Oct 26, 2020
Contributor
|
We need to make sure that the 3.1-preview.3 swagger file also contains all of the contents of v3.1-preview.2. It might be easier to make a copy of the v3.1-preview.2 swagger file, update version number and then copy over the changes necessary for Healthcare and Analyze. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tjprescott
approved these changes
Oct 27, 2020
giromm2ms
pushed a commit
to giromm2ms/azure-rest-api-specs
that referenced
this pull request
Dec 20, 2020
…Azure#11388) * Adds base for updating TextAnalytics from version preview/v3.1-preview.1 to version 2018-05-01-privatepreview * Updates readme * Updates API version in new specs and examples * v3.2-preview.1 /analyze + examples * Adding tasks * Adding Healthcare * Healthcare example * Removing displayName from healthcare example * Restore v3.1-preview.1 and new v3.2-preview.1 folder * Restoring v3.1-preview.1 swagger * Removing some obsolete settings from readme.md * Adding error examples * Fixing LD swagger + examples * Fixing KPE example * PII redactedText in the right place * Addressing linting issues * More linting errors + file name typo * LRO RC from 202 to 204 * Error responses under "error" property in 400/500 * Fixing enum casing * StringIndexType enum casing * Enum as strings + common parameters * NotFound code + fixing date formats * Adding x-ms-parameter-location to global parameters * CustomEntity confirms to TA batch * Changing back to 202 RC on LRO * Flipping delete and get operation order * PHI description + analyze state creation date update * Adding descriptions to healthcare entities + example updates * Removing polymorph types on /analyze * Removing TextAnalyticsResult ref * Removing left-over type property from task results * Update TextAnalytics.json * Moving redacted text to the document level instead of entity level * Changed 204 response to 202 for Healthcare job deletion * fix breaking changes and swagger lint * fix prettier * fix warnings for auto rest * fix healthcareentity * fix prettier * remove 404 and 500 from analyze and health * add suppression for 202 LongRunningResponseStatusCode * removing multi api section (deprecated) * removing custom text variables from swagger and examples * Local changes to readme files * Removed TextAnalyticsTask definition and updated other definitions that inherited its properties * remove multi api section (deprecated)) * reverting back the readme changes * update StringIndexType to StringIndexTypeResponse in one of the enums * update 3.2-preview.1 to 3.1-preview.3 * remove sentiment task * remove entitylinking tasks * fix analyze example * remove sentiment task def Co-authored-by: Assaf Israel <assaf.israel@microsoft.com> Co-authored-by: Abigail Hahn <abhahn@microsoft.com> Co-authored-by: Suhas Mehta <suhas.mehta@microsoft.com>
This file contains hidden or 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
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.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.