-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[DRAFT] Summarization Sync/Streaming API #22132
base: main
Are you sure you want to change the base?
Conversation
Hi, @wangyuantao Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
generate.json | 2023-04-01(6b9c089) | 2023-04-01(main) |
Rule | Message |
---|---|
1038 - AddedPath |
The new version is adding a path that was not found in the old version. New: cognitiveservices/data-plane/Language/generate.json#L28:5 |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
LintDiff: 2 Errors, 6 Warnings failed [Detail]
compared tags (via openapi-validator v2.0.0) | new version | base version |
---|---|---|
release_2023-04-01 | release_2023-04-01(6b9c089) | release_2023-04-01(main) |
[must fix]The following errors/warnings are introduced by current PR:
Rule | Message | Related RPC [For API reviewers] |
---|---|---|
HostParametersValidation |
The host parameter must be called 'endpoint'. Location: cognitiveservices/data-plane/Language/generate.json#L22 |
|
HostParametersValidation |
The host parameter must be typed 'type 'string', format 'url''. Location: cognitiveservices/data-plane/Language/generate.json#L22 |
|
Error response should contain a x-ms-error-code header. Location: cognitiveservices/data-plane/Language/generate.json#L44 |
||
Don't specify additionalProperties as a sibling of properties. Location: cognitiveservices/data-plane/Language/generate.json#L46 |
||
OperationId should be of the form 'Noun_Verb' Location: cognitiveservices/data-plane/Language/generate.json#L53 |
||
Parameter should have a description. Location: cognitiveservices/data-plane/Language/generate.json#L61 |
||
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/generate.json#L89 |
||
Property should have a description. Location: cognitiveservices/data-plane/Language/generate.json#L147 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
~[Staging] ServiceAPIReadinessTest succeeded [Detail] [Expand]
Validation passes for ServiceAPIReadinessTest.
️❌
SwaggerAPIView: 0 Errors, 1 Warnings failed [Detail]
Rule | Message |
---|---|
"How to fix":"Check the readme file and make sure the readme file format is valid and the tag is defined. Use the provided readme template" |
️️✔️
CadlAPIView succeeded [Detail] [Expand]
️❌
ModelValidation: 4 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
INVALID_REQUEST_PARAMETER |
api-version 2023-05-01 is not equal to swagger version Url: cognitiveservices/data-plane/Language/generate.json#L29:15 ExampleUrl: Language/examples/generate/SuccessfulExtractiveSummarizationRequest.json#L2:17 |
INVALID_REQUEST_PARAMETER |
api-version 2023-05-01 is not equal to swagger version Url: cognitiveservices/data-plane/Language/generate.json#L29:15 ExampleUrl: Language/examples/generate/SuccessfulAbstractiveSummarizationRequest.json#L2:17 |
INVALID_REQUEST_PARAMETER |
api-version 2023-05-01 is not equal to swagger version Url: cognitiveservices/data-plane/Language/generate.json#L29:15 ExampleUrl: Language/examples/generate/SuccessfulConversationSummarizationRequest.json#L2:17 |
OBJECT_ADDITIONAL_PROPERTIES |
Additional properties not allowed: conversationItems Url: cognitiveservices/data-plane/Language/generate.json#L164:38 ExampleUrl: Language/examples/generate/SuccessfulConversationSummarizationRequest.json#L6:13 |
️️✔️
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.
Swagger Generation Artifacts
|
Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
NewApiVersionRequired reason: |
@@ -30,6 +30,7 @@ input-file: | |||
- analyzeconversations-authoring.json | |||
- questionanswering.json | |||
- questionanswering-authoring.json | |||
- generate.json |
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.
Is this file name temporary? Will this be going into another file, or is there a more descriptive file name that would be more obvious e.g., "summarization.json"?
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.
I will create a feature branch for generative skills, and create another PR target against that feature branch to add summarization specific sync/stream API. The current PR mixed 2 purposes.
}, | ||
"SummarizationTask": { | ||
"type": "object", | ||
"description": "The summarization task.", |
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.
describe this is abstract
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Data Plane API - Pull Request
Design doc, hero scenarios and core concepts
https://microsoft.sharepoint.com/:p:/t/TextAnalyticsTeam/EaHfvJU41pFAvcTSfHrEXcYBLS4XOOMquE6s1zngQZhJJA?e=hM2IOQ
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.
Is this review for (select one):
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.
❔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
fix #22181