Open samvaity opened 3 days ago
TypeSpec Validation
has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guideLanguage | Package Name | ApiView Link |
---|---|---|
JavaScript | @azure-rest/ai-document-intelligence | https://apiview.dev/Assemblies/Review/0ca4eda857b94249aa787305a387271f?revisionId=df668de4887f4e5980a60120463974f9 |
Python | azure-ai-documentintelligence | https://apiview.dev/Assemblies/Review/e537ef4f04a343e1863478cb96d48b59?revisionId=3b3a9bab7e794c35a7ca70581d4280a1 |
TypeSpec | DocumentIntelligence | https://apiview.dev/Assemblies/Review/f8a22c44fd034f7597acfffdba53dade?revisionId=81599968a1bb42f8946c72f6e0c7a143 |
API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.App Microsoft.Authorization Microsoft.DocumentDB preview
For (2), if there is no customization in your SDK, you may just delete the src/main
folder to clean up the previous files, then tsp-client update
to generate new (emitter does not know whether you have customization, so it won't do this for you).
I've made Java-specific updates in the pull request at https://github.com/Azure/azure-rest-api-specs/pull/31522. Here are a few notes on the typespec generation:
Renaming URL and base64 source fields in
ClassifyDocumentRequest
andAnalyzeDocumentRequest
for Java doesn't update the corresponding documentation.Changing model names creates new models without deleting the old ones.
Need advice on renaming
AnalyzeDocumentFromBase64
toAnalyzeDocumentFromBytes
and updating its content to excludebase64
references.@srnagar, @weidongxu-microsoft, could you provide any insights on these points?