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
[Text Translation] Updating to the latest TypeSpec #40035
Conversation
API change check APIView has identified API level changes in this PR and created following API reviews. |
...translation-text/src/main/java/com/azure/ai/translation/text/TextTranslationAsyncClient.java
Outdated
Show resolved
Hide resolved
...translation-text/src/main/java/com/azure/ai/translation/text/TextTranslationAsyncClient.java
Show resolved
Hide resolved
...translation-text/src/main/java/com/azure/ai/translation/text/TextTranslationAsyncClient.java
Outdated
Show resolved
Hide resolved
String clientTraceId, String from, TextType textType, String category, ProfanityAction profanityAction, | ||
ProfanityMarker profanityMarker, Boolean includeAlignment, Boolean includeSentenceLength, String suggestedFrom, | ||
String fromScript, String toScript, Boolean allowFallback) { | ||
private Mono<List<TranslatedTextItem>> translate(List<String> targetLanguages, List<InputTextItem> body, |
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.
nit: instead of body
can we name the param inputTexts
on all these APIs?
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.
My understanding is that it would require TypeSpec change as some parameters named body
are in generated methods. I can change not generated, but then it will not be consistent.
Description