Skip to content

docs(sqlalchemy-spanner): Added docs support to sqlalchemy-spanner#16195

Open
gkevinzheng wants to merge 2 commits intomainfrom
sqlalchemy-spanner-docs
Open

docs(sqlalchemy-spanner): Added docs support to sqlalchemy-spanner#16195
gkevinzheng wants to merge 2 commits intomainfrom
sqlalchemy-spanner-docs

Conversation

@gkevinzheng
Copy link
Copy Markdown
Contributor

Adds docs support so that our docs pipeline does not fail.

@gkevinzheng gkevinzheng requested review from a team as code owners March 26, 2026 21:22
Copy link
Copy Markdown
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

This pull request enables documentation generation for the sqlalchemy-spanner package by adding a comprehensive README.rst, Sphinx configuration (conf.py), custom CSS, and HTML templates. It also updates the noxfile.py to install necessary dependencies and execute the sphinx-build process. The review feedback identifies a broken link to the samples directory, several typos in the documentation text, and a copy-paste error in the configuration file header.

Comment on lines +64 to +65
The `samples directory <https://github.com/googleapis/google-cloud-python/blob/-/samples/README.md>`__
contains multiple examples for how to configure and use common Spanner features.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This link to the samples directory appears to be broken. It points to a generic samples README.md at the root of the repository, but it should likely point to the specific samples for sqlalchemy-spanner. Please verify the correct path to the samples and update the link.

# for SQLAlchemy 1.4 and 2.0:
spanner+spanner:///projects/project-id/instances/instance-id/databases/database-id

To pass your custom client object directly to be be used, create engine as following:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

There's a typo here. 'to be be used' should be 'to be used'.

Suggested change
To pass your custom client object directly to be be used, create engine as following:
To pass your custom client object directly to be used, create engine as following:

| Cloud Spanner dialect includes two dialect-specific arguments for
``Table`` constructor, which help to define interleave relations:
``spanner_interleave_in`` - a parent table name
``spanner_inverleave_on_delete_cascade`` - a flag specifying if
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

There's a typo in spanner_inverleave_on_delete_cascade. It should be spanner_interleave_on_delete_cascade.

Suggested change
``spanner_inverleave_on_delete_cascade`` - a flag specifying if
``spanner_interleave_on_delete_cascade`` - a flag specifying if

# See the License for the specific language governing permissions and
# limitations under the License.
##
# google-cloud-dataproc documentation build configuration file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This comment seems to be a copy-paste error from another package. It should refer to sqlalchemy-spanner instead of google-cloud-dataproc.

Suggested change
# google-cloud-dataproc documentation build configuration file
# sqlalchemy-spanner documentation build configuration file

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.

1 participant