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

Translation - Add Support for customized_attribution to translateDocument #3928

Closed
greese-insight opened this issue Feb 2, 2023 · 2 comments
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@greese-insight
Copy link

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Is your feature request related to a problem? Please describe.
We are attempting to apply a customized_attribution to the translateDocument method, but it is not available in the proto/interface.

Describe the solution you'd like
Have a way to set this field.

Describe alternatives you've considered
Requesting the api directly instead of using this package.

Additional context
Add any other context or screenshots about the feature request here.

@greese-insight greese-insight changed the title Translation - Add Support for customized_attribution to translateDocument Translation - Add Support for customized_attribution to translateDocument Feb 2, 2023
@sofisl
Copy link
Contributor

sofisl commented Feb 10, 2023

I've confirmed this is happening, we are updating our protos internally to include this feature.

@sofisl sofisl self-assigned this Feb 10, 2023
@sofisl sofisl added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Feb 10, 2023
@sofisl
Copy link
Contributor

sofisl commented May 24, 2023

This was updated here: #4007. Please reopen if you're still seeing issues!

@sofisl sofisl closed this as completed May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants