chore: complete migration of django-google-spanner to librarian#16748
chore: complete migration of django-google-spanner to librarian#16748jskeet wants to merge 1 commit intogoogleapis:mainfrom
Conversation
The README.rst change is just using a full copy of the parent README.rst instead of an include. (That is then consistent with all other packages.)
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request enables generation for the django-google-spanner library, updates its repository metadata, and replaces the documentation include with a comprehensive README. Review feedback identifies several syntax issues in the new documentation, including incorrect reStructuredText link formatting, the use of Markdown link syntax instead of RST, and a lowercase boolean literal in a Python code example.
| <https://docs.djangoproject.com/en/3.2/>`_, and `Django 4.2 | ||
| <https://docs.djangoproject.com/en/4.2/>`_. | ||
| Both versions are long-term support (LTS) releases for the | ||
| `Django project<https://www.djangoproject.com/download/#supported-versions>_`. |
There was a problem hiding this comment.
The reStructuredText link syntax is incorrect. It is missing a space before the opening angle bracket for the link text. Additionally, using a double underscore __ is preferred for anonymous inline links to match the style used elsewhere in this file.
| `Django project<https://www.djangoproject.com/download/#supported-versions>_`. | |
| Django project <https://www.djangoproject.com/download/#supported-versions>__. |
| 'PROJECT': '$PROJECT', | ||
| 'INSTANCE': '$INSTANCE', | ||
| 'NAME': '$DATABASE', | ||
| 'RANDOM_ID_GENERATION_ENABLED': false, |
There was a problem hiding this comment.
In Python, the boolean literal for false is False (capitalized). Since this is inside a .. code:: python block, it should follow Python syntax.
| 'RANDOM_ID_GENERATION_ENABLED': false, | |
| 'RANDOM_ID_GENERATION_ENABLED': False, |
|
|
||
| Django version 4.2 and higher by default supports transactions in autocommit mode. | ||
| A transaction is automatically started if you define an | ||
| [atomic block](https://docs.djangoproject.com/en/4.2/topics/db/transactions/#controlling-transactions-explicitly). |
There was a problem hiding this comment.
This line uses Markdown link syntax text, but the file is in reStructuredText (RST) format. It should be converted to RST link syntax.
| [atomic block](https://docs.djangoproject.com/en/4.2/topics/db/transactions/#controlling-transactions-explicitly). | |
| atomic block <https://docs.djangoproject.com/en/4.2/topics/db/transactions/#controlling-transactions-explicitly>__. |
|
Switching to draft until presubmits are green |
|
@ohmayr , We'll need to disable the failing tests, file a bug to follow up on it and disable releases for this package while we investigate |
|
We may be able to wait for #16624 |
3 participants
The README.rst change is just using a full copy of the parent README.rst instead of an include. (That is then consistent with all other packages.)