chore(migration): Migrate code from googleapis/python-documentai-toolbox into packages/google-cloud-documentai-toolbox

[parthea]

See #11026.

This PR should be merged with a merge-commit, not a squash-commit, in order to preserve the git history.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 migrating the Document AI Toolbox code from the googleapis/python-documentai-toolbox repository into a dedicated package within the google-cloud-documentai-toolbox repository. This involves moving the source code, tests, and documentation, as well as setting up the necessary infrastructure for continuous integration, linting, and release management. The goal is to consolidate the codebase and improve maintainability.

Highlights

• Code Migration: Migrated the googleapis/python-documentai-toolbox code into the packages/google-cloud-documentai-toolbox directory.
• Dependency Management: Introduced new files for dependency management, linting, testing, and release automation.
• Repository Configuration: Added various configuration files for GitHub actions, code owners, issue templates, and repository synchronization.

Activity

• The PR description requests a merge-commit to preserve git history.
• The PR introduces a large number of new files, primarily for configuration and automation.

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. ↩

[gemini-code-assist]

Code Review

This PR migrates the python-documentai-toolbox library into this repository. The changes consist of adding a large number of files for the new package, including source code, tests, samples, and configuration. The code is generally well-structured and tested. My feedback focuses on making the code more robust and maintainable, addressing a potential bug in file handling, and improving code clarity and type correctness.

_{Note: Security Review is unavailable for this PR.}

[gemini-code-assist]

The _get_bytes function does not handle cases where one of the expected files (annotation, config, or PDF) is missing in the GCS directory. If a file is not found, an UnboundLocalError will be raised when trying to access variables like annotation_blob, metadata_blob, or doc_blob. It would be more robust to initialize these variables to None before the loop and add a check to ensure all required files are found before proceeding. This would provide a clearer FileNotFoundError.

[gemini-code-assist]

In the call to _convert_bbox_units for the y_min coordinate, the width parameter is used to pass block.page_height. This is confusing as the function signature for _convert_bbox_units includes a height parameter. Using the height parameter would make the code more readable and less prone to errors.

Suggested change

	y_min = _convert_bbox_units(
	block.bounding_box[f"{block.bounding_y}"],
	input_bbox_units=block.bounding_unit,
	width=block.page_height,
	multiplier=y_multiplier,
	)
	y_min = _convert_bbox_units(
	block.bounding_box[f"{block.bounding_y}"],
	input_bbox_units=block.bounding_unit,
	height=block.page_height,
	multiplier=y_multiplier,
	)

[gemini-code-assist]

The type hint for the v variable is vision.Vertex, but it is initialized as a list []. This is incorrect as vision.Vertex represents a single vertex object, not a list of them. To improve code clarity and correctness for static analysis tools, the type hint should be changed to List[Dict[str, int]] or List[vision.Vertex].

Suggested change

	v: vision.Vertex = []
	v: List[Dict[str, int]] = []