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

Duplicate the BaseResolution in analyze-text and analyze-conversations #21526

Merged
merged 2 commits into from
Nov 17, 2022

Conversation

bidisha-c
Copy link
Member

Data Plane API - Pull Request

Duplicate the BaseResolution in analyze-text and analyze-conversations. The currencyResolution property "ISO4271" has a type mismatch between CLU and NER. Additionally SpeedResolution units values differ.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your engagement record.

  • Link to engagement record issue:

Is this review for (select one):

  • a private preview
  • a public preview
  • GA release

Change Scope

This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

  • Design Document:
  • Previous Open API Doc:
  • Updated paths:

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Guidelines & Specifications

Helpful Links

@bidisha-c bidisha-c requested review from JeffreyRichter and bexxx and removed request for a team November 11, 2022 18:04
@openapi-workflow-bot
Copy link

Hi, @bidisha-c Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

  • Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 11, 2022

    Swagger Validation Report

    ️❌BreakingChange: 50 Errors, 0 Warnings failed [Detail]
    compared swaggers (via Oad v0.10.2)] new version base version
    analyzeconversations.json 2023-05-01(dc50a14) 2023-05-01(main)
    analyzetext.json 2023-05-01(dc50a14) 2023-05-01(main)
    common.json 2023-05-01(dc50a14) 2023-05-01(main)
    analyzeconversations.json 2022-10-01-preview(dc50a14) 2022-10-01-preview(main)
    analyzetext.json 2022-10-01-preview(dc50a14) 2022-10-01-preview(main)
    common.json 2022-10-01-preview(dc50a14) 2022-10-01-preview(main)
    analyzeconversations.json 2022-05-01(dc50a14) 2022-05-01(main)

    Only 16 items are listed, please refer to log for more details.

    Rule Message
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'AgeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'VolumeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'SpeedResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'AreaResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'LengthResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'InformationResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemperatureResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'WeightResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'CurrencyResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'BooleanResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'DateTimeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'NumberResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'OrdinalResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemporalSpanResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'NumericRangeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemporalModifier' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: cognitiveservices/data-plane/Language/common.json#L9:3
    ️❌Breaking Change(Cross-Version): 20 Errors, 45 Warnings failed [Detail]
    compared swaggers (via Oad v0.10.2)] new version base version
    analyzeconversations.json 2023-05-01(dc50a14) 2022-05-01(main)
    analyzeconversations.json 2023-05-01(dc50a14) 2022-10-01-preview(main)
    analyzetext.json 2023-05-01(dc50a14) 2022-05-01(main)
    analyzetext.json 2023-05-01(dc50a14) 2022-10-01-preview(main)
    common.json 2023-05-01(dc50a14) 2022-05-01(main)
    common.json 2023-05-01(dc50a14) 2022-10-01-preview(main)

    The following breaking changes are detected by comparison with the latest stable version:

    Only 16 items are listed, please refer to log for more details.

    Rule Message
    1023 - TypeFormatChanged The new version has a different format than the previous one.
    New: cognitiveservices/data-plane/Language/analyzeconversations.json#L1345:9
    Old: Language/stable/2022-05-01/analyzeconversations.json#L1221:9
    1026 - TypeChanged The new version has a different type 'number' than the previous one 'string'.
    New: cognitiveservices/data-plane/Language/analyzeconversations.json#L1345:9
    Old: Language/stable/2022-05-01/analyzeconversations.json#L1221:9
    1034 - AddedRequiredProperty The new version has new required property 'entities' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'relations' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'id' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'warnings' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'entities, relations, id, warnings' that was not found in the old version.
    New: cognitiveservices/data-plane/Language/analyzetext.json#L834:11
    Old: Language/stable/2022-05-01/analyzetext.json#L779:11
    1034 - AddedRequiredProperty The new version has new required property 'entities' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'id' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'warnings' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'entities, id, warnings' that was not found in the old version.
    New: cognitiveservices/data-plane/Language/analyzetext.json#L1505:11
    Old: Language/stable/2022-05-01/analyzetext.json#L1430:11
    1034 - AddedRequiredProperty The new version has new required property 'entities' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'id' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'warnings' that was not found in the old version.
    1034 - AddedRequiredProperty The new version has new required property 'entities, id, warnings' that was not found in the old version.
    New: cognitiveservices/data-plane/Language/analyzetext.json#L1658:11
    Old: Language/stable/2022-05-01/analyzetext.json#L1559:11
    1034 - AddedRequiredProperty The new version has new required property 'redactedText' that was not found in the old version.


    The following breaking changes are detected by comparison with the latest preview version:

    Only 16 items are listed, please refer to log for more details.

    Rule Message
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'AgeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'VolumeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'SpeedResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'AreaResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'LengthResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'InformationResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemperatureResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'WeightResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'CurrencyResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'BooleanResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'DateTimeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'NumberResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'OrdinalResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemporalSpanResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'NumericRangeResolution' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TemporalModifier' removed or renamed?
    New: cognitiveservices/data-plane/Language/common.json#L9:3
    Old: Language/preview/2022-10-01-preview/common.json#L9:3
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️LintDiff: 6 Warnings warning [Detail]
    compared tags (via openapi-validator v2.0.0) new version base version
    release_2022-07-01-preview release_2022-07-01-preview(dc50a14) release_2022-07-01-preview(main)
    release_2022_05_01 release_2022_05_01(dc50a14) release_2022_05_01(main)
    release_2022_10_01_preview release_2022_10_01_preview(dc50a14) release_2022_10_01_preview(main)

    [must fix]The following errors/warnings are introduced by current PR:

    Rule Message Related RPC [For API reviewers]
    ⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
    Location: cognitiveservices/data-plane/Language/analyzeconversations.json#L1269
    ⚠️ PropertyDescription Property should have a description.
    Location: cognitiveservices/data-plane/Language/analyzeconversations.json#L1269
    ⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L2172
    ⚠️ PropertyDescription Property should have a description.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L2172
    ⚠️ EnumInsteadOfBoolean Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L2172
    ⚠️ PropertyDescription Property should have a description.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L2172


    The following errors/warnings exist before current PR submission:

    Only 16 items are listed, please refer to log for more details.

    Rule Message
    HostParametersValidation The host parameter must be called 'endpoint'.
    Location: cognitiveservices/data-plane/Language/analyzeconversations.json#L39
    HostParametersValidation The host parameter must be typed 'type 'string', format 'url''.
    Location: cognitiveservices/data-plane/Language/analyzeconversations.json#L39
    HostParametersValidation The host parameter must be called 'endpoint'.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L39
    HostParametersValidation The host parameter must be typed 'type 'string', format 'url''.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L39
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L2759
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L3190
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L3193
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L3196
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: cognitiveservices/data-plane/Language/analyzetext.json#L3199
    HostParametersValidation The host parameter must be called 'endpoint'.
    Location: Language/preview/2022-10-01-preview/analyzeconversations.json#L39
    HostParametersValidation The host parameter must be typed 'type 'string', format 'url''.
    Location: Language/preview/2022-10-01-preview/analyzeconversations.json#L39
    HostParametersValidation The host parameter must be called 'endpoint'.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L39
    HostParametersValidation The host parameter must be typed 'type 'string', format 'url''.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L39
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L2759
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L3190
    IntegerTypeMustHaveFormat The integer type does not have a format, please add it.
    Location: Language/preview/2022-10-01-preview/analyzetext.json#L3193
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️️✔️~[Staging] ServiceAPIReadinessTest succeeded [Detail] [Expand]
    Validation passes for ServiceAPIReadinessTest.
    ️❌~[Staging] SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
    ️❌ModelValidation: 20 Errors, 0 Warnings failed [Detail]

    Only 16 items are listed, please refer to log for more details.

    Rule Message
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzeconversations.json#L127:22
    ExampleUrl: Language/examples/conversations/SuccessfulConversationPIISubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzeconversations.json#L127:22
    ExampleUrl: Language/examples/conversations/SuccessfulConversationSummarySubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzeconversations.json#L127:22
    ExampleUrl: Language/examples/conversations/SuccessfulConversationSummarizationTaskSubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzeconversations.json#L127:22
    ExampleUrl: Language/examples/conversations/SuccessfulConversationSentimentSubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzeconversations.json#L225:22
    ExampleUrl: Language/examples/conversations/SuccessfulAnalyzeConversationsJobsCancelRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzetext.json#L137:22
    ExampleUrl: Language/examples/text/SuccessfulAnalyzeTextJobsMultipleTaskSubmitRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzetext.json#L137:22
    ExampleUrl: Language/examples/text/SuccessfulHealthcarePostRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzetext.json#L137:22
    ExampleUrl: Language/examples/text/SuccessfulAbstractiveSummarizationTaskSubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzetext.json#L137:22
    ExampleUrl: Language/examples/text/SuccessfulHealthcareDocumentTypePostRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: cognitiveservices/data-plane/Language/analyzetext.json#L241:22
    ExampleUrl: Language/examples/text/SuccessfulAnalyzeTextJobsCancelRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzeconversations.json#L127:22
    ExampleUrl: 2022-10-01-preview/examples/conversations/SuccessfulConversationPIISubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzeconversations.json#L127:22
    ExampleUrl: 2022-10-01-preview/examples/conversations/SuccessfulConversationSummarySubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzeconversations.json#L127:22
    ExampleUrl: 2022-10-01-preview/examples/conversations/SuccessfulConversationSummarizationTaskSubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzeconversations.json#L127:22
    ExampleUrl: 2022-10-01-preview/examples/conversations/SuccessfulConversationSentimentSubmit.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzeconversations.json#L225:22
    ExampleUrl: 2022-10-01-preview/examples/conversations/SuccessfulAnalyzeConversationsJobsCancelRequest.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Language/preview/2022-10-01-preview/analyzetext.json#L137:22
    ExampleUrl: 2022-10-01-preview/examples/text/SuccessfulAnalyzeTextJobsMultipleTaskSubmitRequest.json
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️️✔️CadlValidation succeeded [Detail] [Expand]
    Validation passes for CadlValidation.
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 11, 2022

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking

    ️⚠️ azure-sdk-for-net-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from b32e189. SDK Automation 14.0.0
      command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
      warn	File azure-sdk-for-net_tmp/initOutput.json not found to read
      command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
      warn	No file changes detected after generation
      warn	Skip detect changed packages
    ️⚠️ azure-sdk-for-python warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from b32e189. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      warn		specification/cognitiveservices/data-plane/Language/readme.md skipped due to azure-sdk-for-python not found in swagger-to-sdk
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh]
      cmderr	[automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.1.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.1.2` to update!
      cmderr	[automation_generate.sh] npm notice
      warn	No file changes detected after generation
      warn	No package detected after generation
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 11, 2022

    Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

    @AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-FixRequiredOnFailure data-plane NewApiVersionRequired labels Nov 11, 2022
    @openapi-workflow-bot
    Copy link

    Hi @bidisha-c, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
    Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
    If you want to know the production traffic statistic, please see ARM Traffic statistic.
    If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.
    Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

    @openapi-workflow-bot
    Copy link

    Hi @bidisha-c, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

    TaskHow to fixPriority
    AvocadoFix-AvocadoHigh
    Semantic validationFix-SemanticValidation-ErrorHigh
    Model validationFix-ModelValidation-ErrorHigh
    LintDiffFix-LintDiffhigh
    If you need further help, please feedback via swagger feedback.

    @openapi-workflow-bot
    Copy link

    NewApiVersionRequired reason:

    A service’s API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service’s contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.

    EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can’t trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

    "x-ms-discriminator-value": "OrdinalResolution",
    "properties": {
    "offset": {
    "type": "string",
    Copy link
    Member

    @mssfang mssfang Nov 11, 2022

    Choose a reason for hiding this comment

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

    Is this should be a numerical value?

    "offset": {
    "type": "integer",
    "description": ".......",
    "format": "int32"
    },

    Copy link
    Member Author

    Choose a reason for hiding this comment

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

    no this should be a string as existing

    Copy link
    Member

    Choose a reason for hiding this comment

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

    Thanks for your answer. Do you have an example or reason for this offset to be a String type?

    "description": "The DateTime SubKind"
    },
    "value": {
    "type": "string",
    Copy link
    Member

    @mssfang mssfang Nov 14, 2022

    Choose a reason for hiding this comment

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

    Copy link
    Member

    Choose a reason for hiding this comment

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

    @mssfang, I was thinking that the "date-time" format should be added to the "TimeExpression" definition instead. However, I haven't confirmed that the service actually returns the right format, which is supposed to be RFC3339 according to the OpenAPI specification 2.0. Do you know if the service returns this correctly?

    Copy link
    Member

    Choose a reason for hiding this comment

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

    I think you are right. Btw, do you know what is an example of Set looks like?

    Copy link
    Member

    @kristapratico kristapratico left a comment

    Choose a reason for hiding this comment

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

    This updates the swagger specs to reflect what the service actually returns.

    Explanation of changes per @joseharriaga:

    1. The value property of NumberResolutions must be changed from string to double.
    2. The ISO4217 (all uppercase) property of CurrencyResolutions must be changed to iso4271 (all lowercase) to match what the service returns in version 2022-10-01-preview. However, this would be a breaking change, because CLU already GA’ed this property. One option is to remove CurrencyResolutions from common.json and have one for CLU (unchanged, all uppercase) and another one for Text Analytics (all lowercase). Then, in the next API version, they can be merged back into the desired state, i.e., a single definition in common.json (all uppsercase).
    3. The possible values of the SpeedUnit enum (some plurals, some singulars) must be changed to match what the service returns in version 2022-10-01-preview (all singulars). Note that the same concerns for breaking changes apply here since CLU already GA’ed this enum too. Additionally, Bidisha mentioned that the desired state is actually all plurals, so the swagger spec can be updated in the next API to match that.
      "KilometersPerHour", => KilometerPerHour
      "KilometersPerMinute", => KilometerPerMinute
      "KilometersPerSecond", => KilometerPerSecond
      "MilesPerHour", => MilePerHour
      "Knot", => Knot ✅
      "FootPerSecond", => FootPerSecond ✅
      "FootPerMinute", => FootPerMinute ✅
      "YardsPerMinute", => YardPerMinute
      "YardsPerSecond", => YardPerSecond
      "MetersPerMillisecond", => MeterPerMillisecond
      "CentimetersPerMillisecond", => CentimeterPerMillisecond
      "KilometersPerMillisecond", => KilometerPerMillisecond

    Copy link
    Member

    @mssfang mssfang left a comment

    Choose a reason for hiding this comment

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

    looks good to me! Thank you for answering my questions

    @heaths
    Copy link
    Member

    heaths commented Nov 16, 2022

    At least for CLU .NET, the "ISO" -> "iso" won't be breaking because we don't generate models currently.

    But why was BaseResolution moved from common to other swaggers? It's not easy to diff since it's across different files.

    @heaths
    Copy link
    Member

    heaths commented Nov 17, 2022

    After talking with @kristapratico offline to understand the changes better, I understand this is a correction to what the service returns. From copying and pasting snippets out to diff manually, I see the following changes:

    1. common.json to analyzeconversations.json: 1 string to number/double format.
    2. common.json to analyzetext.json:
      1. same 1 string to number/double format
      2. "ISO4217" to "iso4217"
      3. several enum values from plural to singular e.g., "MilesPerHour" to "MilePerHour" but only for TA preview

    @heaths heaths added Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 Approved-ModelValidation labels Nov 17, 2022
    @heaths heaths merged commit b32e189 into Azure:main Nov 17, 2022
    anandanthony pushed a commit to anandMicro/azure-rest-api-specs that referenced this pull request Dec 16, 2022
    Azure#21526)
    
    * Duplicate the BaseResolution in analyze-text and analyze-conversations
    
    * Address comments
    kayousef-zz pushed a commit to kayousef-zz/azure-rest-api-specs that referenced this pull request Dec 21, 2022
    Azure#21526)
    
    * Duplicate the BaseResolution in analyze-text and analyze-conversations
    
    * Address comments
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 Approved-ModelValidation BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-FixRequiredOnFailure Cognitive - Language Cognitive Services data-plane NewApiVersionRequired
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    6 participants