Skip to content

Conversation

@bmunkholm
Copy link
Contributor

@bmunkholm bmunkholm commented May 28, 2025

About

Remove page local toc and Project info section as it's redundant.

Preview

https://sqlalchemy-cratedb--220.org.readthedocs.build/

@coderabbitai
Copy link

coderabbitai bot commented May 28, 2025

Walkthrough

The changes remove local table of contents rubrics and directives from multiple documentation files and delete the centralized index-all documentation page. The main index file is simplified, with detailed project information and navigation links consolidated or removed. No code or public API changes are included.

Changes

Files / Groups Change Summary
docs/advanced-querying.rst
docs/crud.rst
docs/dataframe.rst
docs/getting-started.rst
docs/install.rst
docs/overview.rst
docs/working-with-types.rst
Removed "Table of Contents" rubric and local contents directive from each file.
docs/index-all.rst Deleted the centralized index page containing documentation navigation and section links.
docs/index.rst Simplified structure: removed explicit TOC, consolidated project info, removed detailed sections.

Poem

In burrows deep, the docs were pruned,
No more tables at the start,
The index trimmed, the pages tuned,
Simpler paths for every part.
Now rabbits read and hop with glee,
Through streamlined docs—so clear to see!
🐇📚


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dfebefe and 648f287.

📒 Files selected for processing (1)
  • docs/index.rst (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/index.rst
⏰ Context from checks skipped due to timeout of 90000ms (14)
  • GitHub Check: Python: 3.12 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.11 SQLAlchemy: <1.5
  • GitHub Check: Python: 3.10 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.10 SQLAlchemy: <1.5
  • GitHub Check: Python: 3.10 SQLAlchemy: <1.4
  • GitHub Check: Python: 3.9 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.9 SQLAlchemy: <1.4
  • GitHub Check: Python: 3.8 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.8 SQLAlchemy: <1.5
  • GitHub Check: Analyze with SQLAlchemy <2.1
  • GitHub Check: Analyze with SQLAlchemy <1.5
  • GitHub Check: Python: 3.7 SQLAlchemy: <1.4
  • GitHub Check: Run link checker
  • GitHub Check: Analyze with SQLAlchemy <1.4

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a127b3 and bda01e7.

📒 Files selected for processing (9)
  • docs/advanced-querying.rst (0 hunks)
  • docs/crud.rst (0 hunks)
  • docs/dataframe.rst (0 hunks)
  • docs/getting-started.rst (0 hunks)
  • docs/index-all.rst (0 hunks)
  • docs/index.rst (4 hunks)
  • docs/install.rst (0 hunks)
  • docs/overview.rst (0 hunks)
  • docs/working-with-types.rst (0 hunks)
💤 Files with no reviewable changes (8)
  • docs/install.rst
  • docs/working-with-types.rst
  • docs/advanced-querying.rst
  • docs/crud.rst
  • docs/dataframe.rst
  • docs/overview.rst
  • docs/index-all.rst
  • docs/getting-started.rst
⏰ Context from checks skipped due to timeout of 90000ms (17)
  • GitHub Check: Python: 3.13 SQLAlchemy: latest
  • GitHub Check: Python: 3.13 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.13 SQLAlchemy: <1.5
  • GitHub Check: Python: 3.12 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.12 SQLAlchemy: <1.5
  • GitHub Check: Python: 3.11 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.11 SQLAlchemy: <1.4
  • GitHub Check: Python: 3.10 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.9 SQLAlchemy: <2.1
  • GitHub Check: Python: 3.9 SQLAlchemy: <1.5
  • GitHub Check: Python: 3.9 SQLAlchemy: <1.4
  • GitHub Check: Python: 3.8 SQLAlchemy: <2.1
  • GitHub Check: Analyze with SQLAlchemy <2.1
  • GitHub Check: Python: 3.7 SQLAlchemy: <1.5
  • GitHub Check: Analyze with SQLAlchemy <1.5
  • GitHub Check: Python: 3.7 SQLAlchemy: <1.4
  • GitHub Check: Analyze with SQLAlchemy <1.4
🔇 Additional comments (2)
docs/index.rst (2)

55-55: Ensure the reference link target exists for the install page

Please verify that the anchor in docs/install.rst matches :ref:\install`` so that this inline link resolves correctly. Otherwise, consider a fully qualified reference such as:

See also the :ref:`install <install>` page for details.

90-90: These hunks only trim trailing whitespace in code examples and do not change the documentation’s semantics.

Also applies to: 116-116, 119-119

@bmunkholm bmunkholm changed the title Bmunkholm/simplification Docs simplification May 28, 2025
@bmunkholm bmunkholm self-assigned this May 28, 2025
@bmunkholm bmunkholm requested review from amotl and kneth May 28, 2025 10:27
Comment on lines -199 to -231
*******************
Project information
*******************

Resources
=========
- `Source code <https://github.com/crate/sqlalchemy-cratedb>`_
- `Documentation <https://github.com/crate/sqlalchemy-cratedb>`_
- `Python Package Index (PyPI) <https://pypi.org/project/sqlalchemy-cratedb/>`_

Contributions
=============
The SQLAlchemy dialect for CrateDB is an open source project, and is `managed on
GitHub`_.
Every kind of contribution, feedback, or patch, is much welcome. `Create an
issue`_ or submit a patch if you think we should include a new feature, or to
report or fix a bug.

Development
===========
In order to setup a development environment on your workstation, please head
over to the `development sandbox`_ documentation. When you see the software
tests succeed, you should be ready to start hacking.

Page index
==========
The full index for all documentation pages can be inspected at :ref:`index-all`.

License
=======
The project is licensed under the terms of the Apache 2.0 license, like
`CrateDB itself <CrateDB source_>`_, see `LICENSE`_.

Copy link
Member

@amotl amotl May 28, 2025

Choose a reason for hiding this comment

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

Maybe add fragments of those to the project README instead? In this case, we are getting rid of it on the documentation, but still can use it on the GitHub page, which is more distant to the former.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point! I already did check the readme and there isn't anything here that's not already part of the readme apart from the License not being mentioned directly. But I think that's no longer needed since it's shown by Github already in the right sidebar.
Let me know if I overlooked anything.

@amotl
Copy link
Member

amotl commented Jun 2, 2025

Please let me know if you would like to receive guidance on this spot.

docs/install.rst: WARNING: document isn't included in any toctree

@bmunkholm
Copy link
Contributor Author

bmunkholm commented Jun 4, 2025

@amotl I just needed to add "Hidden" in the TOC directive for install page instead of removing it entirely.
One thing I'm slightly confused about though is why a TOC level below the Install page itself is shown now?
image
Since I did set maxdepth to 1.

That's also on other pages. And I would like to remove that as it serves only to clutter now that we have page local righthand TOC. So in general, I think we should only have left hand toc entries for anything that is it's own page, and leave navigation on the page headers to the right hand toc.

@amotl
Copy link
Member

amotl commented Jun 4, 2025

Hi Brian. In full documentation assembly mode, this spot within the CrateDB documentation theme's sidebartoc.html is the source of truth. I guess it is the maxdepth=3 setting which is responsible for expanding the navigation items for the section about the CrateDB SQLAlchemy dialect to that level.

Unfortunately, the spot is in a remote repository, and this certainly qualifies as a general architecture flaw, but c'est la vie: I haven't been able to improve the situation in one way or another yet. It currently is a central place where things are stitched together 1.

Unfortunately, the spot is in a remote repository, and certainly qualifies as a general architecture smell.

Heads up: It could be worse. ;]

Footnotes

  1. Currently, there is no specific educational material for that knowledge just yet, because it has been inherent knowledge with previous generations of editors.

@bmunkholm
Copy link
Contributor Author

Thank you so much for saving me a great deal of headscratching! I will deal with that separately then.

@bmunkholm bmunkholm merged commit 65ca626 into main Jun 6, 2025
30 checks passed
@bmunkholm bmunkholm deleted the bmunkholm/simplification branch June 6, 2025 07:42
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.

4 participants