Skip to content

chore: fix formatting for handwritten translate files#15585

Merged
ohmayr merged 1 commit intomainfrom
fix-translate-formatting
Feb 19, 2026
Merged

chore: fix formatting for handwritten translate files#15585
ohmayr merged 1 commit intomainfrom
fix-translate-formatting

Conversation

@ohmayr
Copy link
Contributor

@ohmayr ohmayr commented Feb 19, 2026

Update handwritten files formatting to be compatible with ruff check.

@ohmayr ohmayr requested review from a team as code owners February 19, 2026 19:32
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ohmayr, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving code consistency and maintainability by applying formatting fixes to handwritten files within the google-cloud-translate package. The changes ensure compatibility with the ruff check linter, making the codebase cleaner and easier to manage.

Highlights

  • Code Formatting: Updated code formatting in __init__.py and client.py to align with ruff check compatibility, primarily by removing unnecessary blank lines and reformatting a string literal.
Changelog
  • packages/google-cloud-translate/google/cloud/translate_v2/init.py
    • Removed an extraneous blank line after the module docstring.
  • packages/google-cloud-translate/google/cloud/translate_v2/client.py
    • Removed an extraneous blank line after the module docstring.
    • Reformatted a multi-line string literal for better readability and ruff compatibility.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request addresses formatting issues in __init__.py and client.py files to align with ruff check requirements. The changes primarily involve removing extra blank lines and reformatting a multi-line string for better readability and consistency. The changes are straightforward and improve code formatting.


"""Google Cloud Translation API wrapper."""


Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Removing this extra blank line improves code formatting and adheres to common Python style guides that discourage excessive blank lines.

Suggested change
from google.cloud.translate import __version__


"""Client for interacting with the Google Cloud Translation API."""


Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Removing this extra blank line improves code formatting and adheres to common Python style guides that discourage excessive blank lines.

Suggested change
import google.api_core.client_options

Comment on lines +177 to 179
len(detections[index]),
)
raise ValueError(message, value, detections[index])
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The reformatting of the message string improves readability by consolidating it into a single line, which is generally preferred for short strings unless multi-line formatting significantly enhances clarity.

                message = ("Expected a single detection per value, API returned %d") % (len(detections[index]),)

@ohmayr ohmayr changed the title chore: fix formating for translate chore: fix formatting for translate Feb 19, 2026
@ohmayr ohmayr force-pushed the fix-translate-formatting branch from df6880d to caa3eb5 Compare February 19, 2026 21:28
@ohmayr ohmayr changed the title chore: fix formatting for translate chore: fix formatting for handwritten translate files Feb 19, 2026
@ohmayr ohmayr merged commit 2b0c979 into main Feb 19, 2026
27 checks passed
@ohmayr ohmayr deleted the fix-translate-formatting branch February 19, 2026 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments